jira

# Jira Issue Management

**Use this skill whenever Jira work is requested.**

## Setup

- Run `./scripts/check-environment.sh`. The skill halts with explicit instructions when `jira` is missing or not authenticated (`jira init` required once).
- Ensure the `jira` CLI remains in PATH after the check.
- Use upstream flags like `--project`, `--board`, etc., for context as needed; no extra configuration lives in the skill.

## Command Pattern

```bash
jira <command> <subcommand> [arguments] [flags]
```

Primary commands: `issue`, `project`, `board`, `sprint`, `epic`, `release`, `open`, `me`, `serverinfo`.

Keep outputs deterministic:

- Run `./scripts/check-environment.sh` at the start of every session; abort work if it reports an error.
- Add `--plain` plus `--columns ...` for TSV tables that stream cleanly.
- Use `--raw` (alias for JSON) when structured data is required.
- Provide explicit ranges via `--paginate start:limit` to cap interactive views.

## Core Workflows

- **Projects** – enumerate available projects  
  ```bash
  jira project list --plain --columns key,name,type
  ```

- **Issues**  
  - Search / filter:
    ```bash
    jira issue list --status Done --assignee "$(jira me)" --plain --columns key,summary,status,assignee
    jira issue search 'project = PROJ AND status = "In Progress"' --plain --columns key,summary,status
    jira issue list --raw --jql 'label = backend' --paginate 0:50
    ```
  - View details: `jira issue view PROJ-123 --plain --comments 5`
  - Create:
    ```bash
    jira issue create \
      --type Bug \
      --summary "API returns 500" \
      --description-file docs/bug.md \
      --priority High \
      --assignee "$(jira me)" \
      --label backend --label urgent
    ```
  - Update:
    ```bash
    jira issue edit PROJ-123 --summary "Refine API contract" --priority Medium
    jira issue move PROJ-123 "In Review" --comment "Ready for QA"
    jira issue assign PROJ-123 user@example.com
    ```
  - Comment / worklog:
    ```bash