Help us improve
Share bugs, ideas, or general feedback.
From jira
Use when work on a ticket has reached a stage boundary — started working, sent for review, completed, blocked, or reopened. Handles status transition, comment, and field updates in one pass.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jira:jira-progressThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Transitions a ticket's status and adds a meaningful comment describing what happened — all in one pass. The comment is the valuable part; a bare status change is cheap.
Share bugs, ideas, or general feedback.
Transitions a ticket's status and adds a meaningful comment describing what happened — all in one pass. The comment is the valuable part; a bare status change is cheap.
| Stage | User says | Comment guidance |
|---|---|---|
start | "start working on", "pick up" | What you're about to do |
review | "send for review", "ready for review" | What was done, what to review |
done | "mark as done", "complete", "finished" | Summary of what was accomplished |
block | "blocked on", "stuck" | What the blocker is and who can unblock |
reopen | "reopen", "needs more work" | Why it's being reopened |
When the user mentions multiple tickets in one request (e.g., "set 3529 to done, 2692 to done, 3365 to in progress"):
config/workflows.jsonacli jira workitem search --jql "key in (K1,K2,K3)" --fields "key,status" --json)acli jira workitem transition --key "K1,K2" --status "TARGET" --yes --ignore-errorsUX-3529: IN PROGRESS → DONE | Comment added
UX-2692: IN REVIEW → DONE | Comment added
UX-3365: GROOMED → IN PROGRESS | Comment added
PL-3718 → PL)config/workflows.json:
config/workflows.json (relative to the plugin root)projects.PROJECT_KEY existsjira-workflow skill for this project. After it completes, re-read the config and continue.projects.PROJECT_KEY.statuses.STAGEtransitions is configured for this project):
acli jira workitem view KEY-123 --fields "status" --jsonacli jira workitem transition --key "KEY-123" --status "RESOLVED_STATUS" --yes
6b. Check required fields — read required_fields from config/workflows.json for the target status:
"DONE": ["resolution"]), note that ACLI cannot set these fields via CLI (verified limitation in acli v1.3.x). Warn the user: "Note: The resolution field is required for DONE but cannot be set via ACLI. It may be set automatically by your workflow, or you can set it manually in Jira."acli jira workitem view KEY-123 --fields "resolution" --json — if the workflow auto-set it, no action needed.acli jira workitem comment create --key "KEY-123" --body "Started work on the API refactor — focusing on the auth endpoints first"
start):acli jira workitem edit --key "KEY-123" --assignee "user@email.com" --yes
KEY-123: PREVIOUS_STATUS → RESOLVED_STATUS | Comment addedIf ACLI returns exit code != 0:
acli jira auth login --web --site <site>.atlassian.netbrew tap atlassian/homebrew-acli && brew install aclijira-workflow with the Rovo path to capture the full transition graph.npx claudepluginhub jackhutson/jira-plugin --plugin jiraProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.