| name | jira-bootstrap |
| argument-hint | <PROJECT-NNN e.g. PROJ-123> [--delegate] [--light] |
| description | Use when starting work on a Jira story — loads the ticket's context (summary, description, acceptance criteria, comments, attachments) into the conversation and downloads attachments by default. --delegate also writes a self-contained context doc for agent handoff. Trigger phrases: "bootstrap PROJ-123", "load jira ticket PROJ-123", "start work on PROJ-123", "jira-bootstrap PROJ-123".
|
Jira Bootstrap
Load a Jira story into the conversation so the agent has full context
before starting investigation, implementation, or planning.
Attachments are downloaded by default — pass --light to skip.
Usage
/jira-bootstrap <ticket-id> # fetch + download attachments
/jira-bootstrap <ticket-id> --delegate # also write a context handoff doc
/jira-bootstrap <ticket-id> --light # fetch only, skip downloading
--delegate and --light are mutually exclusive — if both are passed, ignore
--light and proceed as if only --delegate was given (downloading is required
for the handoff doc to have local file links).
Tool Detection
Before fetching, detect which Jira integration is available and use the best one:
-
Rovo MCP — if mcp__claude_ai_Atlassian_Rovo__ tools are present in the
session, use them. They provide the richest integration (no env var setup,
native auth). Use Rovo tools to fetch the issue and its attachments.
-
jira-cli — if Rovo is unavailable, check:
which jira
If found, use jira issue view <ticket-id> to fetch the story.
-
jira_issue.py (fallback) — if neither of the above is available, use the
bundled script as described in the procedure below.
Procedure (jira_issue.py fallback)
Step 1: Fetch the story
Run:
python3 ~/.claude/scripts/jira_issue.py <ticket-id>
If the script errors on missing env vars (JIRA_URL, JIRA_EMAIL, JIRA_AUTH_TOKEN):
- For
JIRA_URL or JIRA_EMAIL: ask the user for the values, then invoke update-config
to write them into conf/ai/claude/settings.json under env.
- For
JIRA_AUTH_TOKEN: do NOT prompt for the value — guide the user:
- Log into Jira in the browser; confirm the avatar email matches
id.atlassian.com
- Go to
https://id.atlassian.com/manage-profile/security/api-tokens
- Click "Create API token" (plain — NOT "with scopes"), copy immediately
- Add to
~/.claude/settings.local.json: { "env": { "JIRA_AUTH_TOKEN": "<token>" } }
- Start a new Claude Code session so the var is loaded, then retry.
Read the full Markdown output. This gives you: summary, status, type,
priority, assignee, reporter, description (ADF converted to Markdown),
attachment list, and all comments with author and date.
Step 2: Download attachments (skip if --light)
Run:
python3 ~/.claude/scripts/jira_issue.py <ticket-id> download
Files land in /tmp/jira/<ticket-id>/. Read relevant ones (specs, screenshots,
logs) and include their content in your working context.
Step 3: Write context handoff doc (if --delegate)
Run the fetch again with --attachment-dir so the output includes resolved
local file links, then save it to docs/context/<ticket-id>.md:
python3 ~/.claude/scripts/jira_issue.py <ticket-id> \
--attachment-dir /tmp/jira/<ticket-id>
Write the output to docs/context/<ticket-id>.md. This file is
self-contained: description, comments, and a ## Local Files section with
image embeds () and file links ([name](path)) pointing to
the downloaded attachments. A delegated agent can read this file and work
entirely from it without Jira access.
Step 4: Surface context to the conversation
Summarize the ticket in 3–5 sentences: what needs to be done, acceptance
criteria extracted from the description or comments, any blockers or open
questions visible in the thread. Make this the working frame for the session.
Step 5: Proceed
With context loaded and attachments downloaded (unless --light), proceed
with the work the ticket describes. If --delegate was passed, hand off
docs/context/<ticket-id>.md to the target agent.
