Read JIRA Ticket: $ARGUMENTS
All Atlassian operations in this skill go through lisa-atlassian-access. Do not call MCP tools or acli directly.
Fetch the full scope of the ticket AND its related graph. Downstream agents must never act on a ticket in isolation — always call this skill first so they see blockers, epic siblings, linked PRs, and historical comments.
Repository name for scoped comments and logs: basename $(git rev-parse --show-toplevel).
Phase 1 — Resolve Context
- Invoke
lisa-atlassian-access via the Skill tool with operation: list-sites to confirm the configured site is reachable and resolve the cloud ID.
- If $ARGUMENTS is not a ticket key (e.g.
PROJ-123), stop and report. Do NOT guess.
Phase 2 — Fetch Primary Ticket
Invoke lisa-atlassian-access via the Skill tool with operation: read-ticket key: <TICKET-KEY> for the target ticket. The access layer MUST request an explicit full JIRA field set for this operation (acli jira workitem view --fields '*all', REST fields=*all, or an equivalent substrate-specific field list). Do not accept or re-use a default acli workitem view payload; its default six-field response omits parent, components, labels, priority, and custom fields, which makes leaf-only, relationship-search, build-ready, and required-custom-field gates read false-empty data. Extract and preserve:
Metadata
- Key, summary, issue type, status, resolution
- Priority, assignee, reporter, creator
- Labels, components, fix versions, affects versions
- Sprint, story points, original/remaining estimate
- Created, updated, resolved dates
- Parent (epic link or parent issue)
- Custom fields relevant to the project (read every custom field — do not filter)
Body
- Full description (preserve formatting)
- Acceptance criteria section if separately structured
- Validation Journey section if present (pass verbatim to downstream)
- Attachments list — capture
id, filename, mimeType, size, and content URL for each. Do not download unless a downstream task needs the bytes (see "Downloading attachments" below).
Downloading attachments (opt-in)
The Atlassian MCP exposes attachment metadata but no binary-fetch tool (JRACLOUD-97830, ECO-1265). Fetch attachment bytes only when a downstream task explicitly needs them — e.g., a design-fidelity check on an image, log-file analysis, PDF text extraction. For everything else, keep the URL reference and move on.
bash .claude/skills/jira-read-ticket/scripts/download-attachment.sh <id-or-content-url> <output-path>
Requires python3 and JIRA_API_TOKEN. JIRA_SERVER and JIRA_LOGIN prefer environment values, then the project's .lisa/jira-cli/.config.yml, then the announced home config fallback. Missing credentials produce exit code 2 — record the URL only and continue. The server must be a bare HTTPS origin without userinfo, path prefix, query, or fragment. A full attachment URL must use that same origin; invalid destinations are rejected before Basic authorization is constructed. Signed external downloads receive no Basic credentials and use HTTPS only.
After download, branch on mimeType:
image/* — pass the local path to image-aware downstream tools
text/*, application/json, application/xml, application/x-yaml — read inline as text
application/pdf — extract text via downstream tooling if needed
- everything else — record path only; do not attempt to inline binary content
Comments
Fetch ALL comments in chronological order via lisa-atlassian-access operation: comments key: <TICKET-KEY>, which pages until every comment is read — the comments embedded in read-ticket are only the first page. Do not truncate. If the result reports comments_complete: false (a failed page, or an MCP-only read that could not page), say so at the top of the bundle's Comments section with the fetched-versus-total counts, so no downstream agent mistakes a partial set for the whole. For each:
- Author, timestamp, body
- Flag comments that contain: credentials, reproduction steps, status updates from stakeholders, decisions, or triage headers like
[repo-name]
Phase 3 — Fetch Remote Links
The primary ticket payload returned by lisa-atlassian-access operation: read-ticket includes the issue's remote links. If the substrate returns remote links separately, request them via lisa-atlassian-access with operation: read-ticket key: <K> (the operation MUST return remote links — extend atlassian-access if it doesn't). For each remote link:
- GitHub PR or commit (
github.com/.../(pull|commit)/...): run gh pr view <url> --json title,state,body,mergedAt,reviewDecision,comments,reviews (for PRs) or gh api repos/<owner>/<repo>/commits/<sha> (for commits). Capture title, state, body, unresolved review comments, merge status.
- Confluence page: capture title and URL. Do not fetch body unless a downstream task explicitly needs it.
- Dashboard, log link, or external URL: capture title and URL only.
If gh is not authenticated, note "gh auth required" and continue — do not abort.
Phase 4 — Fetch Issue Links (Relationships)
Every linked ticket must be fetched. Do not skip any link type. For each link in the primary ticket's issuelinks field, group by type:
blocks / is blocked by
relates to
duplicates / is duplicated by
clones / is cloned by
- Any other custom link types configured in the project
For each linked ticket, invoke lisa-atlassian-access with operation: read-ticket key: <LINKED-KEY> and capture:
- Key, summary, type, status, resolution
- Description (full, unless closed with resolution
Won't Do/Duplicate — then summary only)
- Acceptance criteria
- Last 10 comments (chronological)
- Remote links (PR URLs and state only — skip deep fetch unless the link is
blocks or is blocked by)
Special handling for is blocked by: fetch the full PR/commit details via gh for each blocker's remote links so the agent knows whether the blocker is actually shipped.
Phase 5 — Fetch Epic Context
If the primary ticket has an epic parent (or IS an epic):
- Fetch the epic itself via
lisa-atlassian-access operation: read-ticket key: <EPIC-KEY> — full description, acceptance criteria, Validation Journey — and its comments, all of them, via lisa-atlassian-access operation: comments key: <EPIC-KEY>.
- Find epic siblings via JQL:
"Epic Link" = <EPIC-KEY> AND key != <TICKET-KEY>
Invoke lisa-atlassian-access with operation: search-issues jql: "<above-JQL>". For each sibling capture: key, summary, type, status, assignee, priority.
- Read each sibling's description at a SUMMARY level (first paragraph only) — the goal is to surface related in-flight work, not duplicate full content. If a sibling is
In Progress or In Review with an assignee different from the current ticket, flag it prominently.
If the primary ticket IS an epic, also fetch all children via the JQL above.
Phase 6 — Fetch Subtasks
If the primary ticket has subtasks, fetch each via lisa-atlassian-access operation: read-ticket key: <SUBTASK-KEY>: key, summary, type, status, assignee, description (first paragraph), acceptance criteria.
Phase 7 — Assemble Context Bundle
Produce a single structured output that the caller can pass verbatim to downstream agents. Use this format:
# Ticket Context: <KEY>
## Primary Ticket
- Key: <KEY>
- Type: <type>
- Status: <status>
- Priority: <priority>
- Assignee: <name>
- Epic: <epic-key> — <epic-summary>
- Sprint: <sprint>
- Labels: <labels>
- Components: <components>
### Description
<full description>
### Acceptance Criteria
<criteria>
### Validation Journey
<section or "None">
### Comments (<fetched> of <total>; comments_complete: <true|false>)
<when incomplete: "INCOMPLETE — <fetched> of <total> comments read via <substrate>">
<chronological comments, flagged items called out>
### Attachments
<list with id, filename, mimeType, size, content URL — note any that were downloaded and their local paths>
## Remote Links
### Pull Requests (<count>)
- <url> — <title> — <state> — <reviewDecision>
<body summary + unresolved review comments>
### Confluence
- <title> — <url>
### Other
- <title> — <url>
## Issue Links
### Blocks (<count>)
<per-ticket block>
### Is Blocked By (<count>)
<per-ticket block with PR state>
### Relates To (<count>)
<per-ticket block>
### Duplicates / Clones
<per-ticket block>
## Epic Context
### Epic <EPIC-KEY> — <summary>
- Status: <status>
- Description: <full>
- Comments: <chronological>
- Validation Journey: <section or None>
### Siblings In-Flight (<count>)
- <KEY> — <status> — <assignee> — <summary> **[FLAG: in progress by other assignee]**
### Other Siblings (<count>)
- <KEY> — <status> — <summary>
## Subtasks (<count>)
- <KEY> — <status> — <assignee> — <summary>
## Summary for Downstream
- Full ticket count pulled: <N>
- Blockers still open: <list>
- Related in-flight work: <list>
- Relevant PRs: <list with state>
Rules
- Never summarize or truncate the primary ticket's description or Validation Journey.
- Never skip a link type, even if it seems unrelated — the agent downstream decides relevance.
- If a linked ticket returns an access error, capture the error and continue. Do not abort the read.
- Flag in-flight sibling work prominently so the caller can avoid duplicate implementation.
- If the ticket has no epic parent, state this explicitly — do not silently skip Phase 5.
- Output is pure context. This skill never modifies the ticket.
1---2name: lisa-jira-read-ticket-33description: "Fetches the full scope of a JIRA ticket — metadata, description, acceptance criteria, all comments, remote links (PRs, Confluence, dashboards), issue links (blocks/is blocked by/relates to/duplicates/clones), epic parent with siblings, and subtasks. Produces a consolidated context bundle that downstream agents consume so they never act on a single ticket in isolation."4allowed-tools: ["Bash", "Skill"]5metadata:6 source: https://skillmd.com/skills/codyswanngt/lisa-jira-read-ticket-37---89# Read JIRA Ticket: $ARGUMENTS1011All Atlassian operations in this skill go through `lisa-atlassian-access`. Do not call MCP tools or `acli` directly.1213Fetch the full scope of the ticket AND its related graph. Downstream agents must never act on a ticket in isolation — always call this skill first so they see blockers, epic siblings, linked PRs, and historical comments.1415Repository name for scoped comments and logs: `basename $(git rev-parse --show-toplevel)`.1617## Phase 1 — Resolve Context18191. Invoke `lisa-atlassian-access` via the Skill tool with `operation: list-sites` to confirm the configured site is reachable and resolve the cloud ID.202. If $ARGUMENTS is not a ticket key (e.g. `PROJ-123`), stop and report. Do NOT guess.2122## Phase 2 — Fetch Primary Ticket2324Invoke `lisa-atlassian-access` via the Skill tool with `operation: read-ticket key: <TICKET-KEY>` for the target ticket. The access layer MUST request an explicit full JIRA field set for this operation (`acli jira workitem view --fields '*all'`, REST `fields=*all`, or an equivalent substrate-specific field list). Do not accept or re-use a default `acli workitem view` payload; its default six-field response omits parent, components, labels, priority, and custom fields, which makes leaf-only, relationship-search, build-ready, and required-custom-field gates read false-empty data. Extract and preserve:2526### Metadata2728- Key, summary, issue type, status, resolution29- Priority, assignee, reporter, creator30- Labels, components, fix versions, affects versions31- Sprint, story points, original/remaining estimate32- Created, updated, resolved dates33- Parent (epic link or parent issue)34- Custom fields relevant to the project (read every custom field — do not filter)3536### Body3738- Full description (preserve formatting)39- Acceptance criteria section if separately structured40- **Validation Journey** section if present (pass verbatim to downstream)41- Attachments list — capture `id`, `filename`, `mimeType`, `size`, and `content` URL for each. Do not download unless a downstream task needs the bytes (see "Downloading attachments" below).4243#### Downloading attachments (opt-in)4445The Atlassian MCP exposes attachment metadata but no binary-fetch tool ([JRACLOUD-97830](https://jira.atlassian.com/browse/JRACLOUD-97830), [ECO-1265](https://jira.atlassian.com/browse/ECO-1265)). Fetch attachment bytes only when a downstream task explicitly needs them — e.g., a design-fidelity check on an image, log-file analysis, PDF text extraction. For everything else, keep the URL reference and move on.4647```bash48bash .claude/skills/jira-read-ticket/scripts/download-attachment.sh <id-or-content-url> <output-path>49```5051Requires `python3` and `JIRA_API_TOKEN`. `JIRA_SERVER` and `JIRA_LOGIN` prefer environment values, then the project's `.lisa/jira-cli/.config.yml`, then the announced home config fallback. Missing credentials produce exit code 2 — record the URL only and continue. The server must be a bare HTTPS origin without userinfo, path prefix, query, or fragment. A full attachment URL must use that same origin; invalid destinations are rejected before Basic authorization is constructed. Signed external downloads receive no Basic credentials and use HTTPS only.5253After download, branch on `mimeType`:54- `image/*` — pass the local path to image-aware downstream tools55- `text/*`, `application/json`, `application/xml`, `application/x-yaml` — read inline as text56- `application/pdf` — extract text via downstream tooling if needed57- everything else — record path only; do not attempt to inline binary content5859### Comments6061Fetch ALL comments in chronological order via `lisa-atlassian-access` `operation: comments key: <TICKET-KEY>`, which pages until every comment is read — the comments embedded in `read-ticket` are only the first page. Do not truncate. If the result reports `comments_complete: false` (a failed page, or an MCP-only read that could not page), say so at the top of the bundle's Comments section with the fetched-versus-total counts, so no downstream agent mistakes a partial set for the whole. For each:62- Author, timestamp, body63- Flag comments that contain: credentials, reproduction steps, status updates from stakeholders, decisions, or triage headers like `[repo-name]`6465## Phase 3 — Fetch Remote Links6667The primary ticket payload returned by `lisa-atlassian-access` `operation: read-ticket` includes the issue's remote links. If the substrate returns remote links separately, request them via `lisa-atlassian-access` with `operation: read-ticket key: <K>` (the operation MUST return remote links — extend `atlassian-access` if it doesn't). For each remote link:6869- **GitHub PR or commit** (`github.com/.../(pull|commit)/...`): run `gh pr view <url> --json title,state,body,mergedAt,reviewDecision,comments,reviews` (for PRs) or `gh api repos/<owner>/<repo>/commits/<sha>` (for commits). Capture title, state, body, unresolved review comments, merge status.70- **Confluence page**: capture title and URL. Do not fetch body unless a downstream task explicitly needs it.71- **Dashboard, log link, or external URL**: capture title and URL only.7273If `gh` is not authenticated, note "gh auth required" and continue — do not abort.7475## Phase 4 — Fetch Issue Links (Relationships)7677Every linked ticket must be fetched. Do not skip any link type. For each link in the primary ticket's `issuelinks` field, group by type:7879- `blocks` / `is blocked by`80- `relates to`81- `duplicates` / `is duplicated by`82- `clones` / `is cloned by`83- Any other custom link types configured in the project8485For each linked ticket, invoke `lisa-atlassian-access` with `operation: read-ticket key: <LINKED-KEY>` and capture:8687- Key, summary, type, status, resolution88- Description (full, unless closed with resolution `Won't Do`/`Duplicate` — then summary only)89- Acceptance criteria90- Last 10 comments (chronological)91- Remote links (PR URLs and state only — skip deep fetch unless the link is `blocks` or `is blocked by`)9293**Special handling for `is blocked by`:** fetch the full PR/commit details via `gh` for each blocker's remote links so the agent knows whether the blocker is actually shipped.9495## Phase 5 — Fetch Epic Context9697If the primary ticket has an epic parent (or IS an epic):98991. Fetch the epic itself via `lisa-atlassian-access` `operation: read-ticket key: <EPIC-KEY>` — full description, acceptance criteria, Validation Journey — and its comments, all of them, via `lisa-atlassian-access` `operation: comments key: <EPIC-KEY>`.1002. Find epic siblings via JQL:101 ```jql102 "Epic Link" = <EPIC-KEY> AND key != <TICKET-KEY>103 ```104 Invoke `lisa-atlassian-access` with `operation: search-issues jql: "<above-JQL>"`. For each sibling capture: key, summary, type, status, assignee, priority.1053. Read each sibling's description at a SUMMARY level (first paragraph only) — the goal is to surface related in-flight work, not duplicate full content. If a sibling is `In Progress` or `In Review` with an assignee different from the current ticket, flag it prominently.106107If the primary ticket IS an epic, also fetch all children via the JQL above.108109## Phase 6 — Fetch Subtasks110111If the primary ticket has subtasks, fetch each via `lisa-atlassian-access` `operation: read-ticket key: <SUBTASK-KEY>`: key, summary, type, status, assignee, description (first paragraph), acceptance criteria.112113## Phase 7 — Assemble Context Bundle114115Produce a single structured output that the caller can pass verbatim to downstream agents. Use this format:116117```text118# Ticket Context: <KEY>119120## Primary Ticket121- Key: <KEY>122- Type: <type>123- Status: <status>124- Priority: <priority>125- Assignee: <name>126- Epic: <epic-key> — <epic-summary>127- Sprint: <sprint>128- Labels: <labels>129- Components: <components>130131### Description132<full description>133134### Acceptance Criteria135<criteria>136137### Validation Journey138<section or "None">139140### Comments (<fetched> of <total>; comments_complete: <true|false>)141<when incomplete: "INCOMPLETE — <fetched> of <total> comments read via <substrate>">142<chronological comments, flagged items called out>143144### Attachments145<list with id, filename, mimeType, size, content URL — note any that were downloaded and their local paths>146147## Remote Links148### Pull Requests (<count>)149- <url> — <title> — <state> — <reviewDecision>150 <body summary + unresolved review comments>151152### Confluence153- <title> — <url>154155### Other156- <title> — <url>157158## Issue Links159### Blocks (<count>)160<per-ticket block>161162### Is Blocked By (<count>)163<per-ticket block with PR state>164165### Relates To (<count>)166<per-ticket block>167168### Duplicates / Clones169<per-ticket block>170171## Epic Context172### Epic <EPIC-KEY> — <summary>173- Status: <status>174- Description: <full>175- Comments: <chronological>176- Validation Journey: <section or None>177178### Siblings In-Flight (<count>)179- <KEY> — <status> — <assignee> — <summary> **[FLAG: in progress by other assignee]**180181### Other Siblings (<count>)182- <KEY> — <status> — <summary>183184## Subtasks (<count>)185- <KEY> — <status> — <assignee> — <summary>186187## Summary for Downstream188- Full ticket count pulled: <N>189- Blockers still open: <list>190- Related in-flight work: <list>191- Relevant PRs: <list with state>192```193194## Rules195196- Never summarize or truncate the primary ticket's description or Validation Journey.197- Never skip a link type, even if it seems unrelated — the agent downstream decides relevance.198- If a linked ticket returns an access error, capture the error and continue. Do not abort the read.199- Flag in-flight sibling work prominently so the caller can avoid duplicate implementation.200- If the ticket has no epic parent, state this explicitly — do not silently skip Phase 5.201- Output is pure context. This skill never modifies the ticket.