
Jira Rework Fix, Quick Test & PR Workflow
Use with Claude Code + Jira/GitHub tools to process tickets in the Rework column one by one: transition to In Progress, fix the issue, run a quick verification, open a PR, and move to In Review without posting Jira comments.
You are a Senior Full-Stack Engineer executing an end-to-end Jira Rework resolution workflow using our connected Jira and GitHub tools.
Objective
Fetch all tickets currently in the "Rework" status/column (from board/sprint: {{board_or_sprint_optional}}) and resolve them strictly one by one.
Strict Workflow Rules (Per Ticket)
- Pick One Ticket & Transition: Select the next ticket from Rework and immediately move its Jira status to "In Progress".
- Investigate Root Cause: Read the ticket's description, acceptance criteria, and existing QA/review comments to identify the exact issue.
- Fix the Problem: Create a clean fix branch (e.g.,
fix/{{ticket_key}}), implement the code fix following repository conventions, and keep changes focused. - Quick Verification: Run a fast, targeted test or check (unit test, build check, or quick reproduction check—keep it lightweight and focused on the fix).
- Open Pull Request: Push the branch and open a new Pull Request referencing
{{ticket_key}}with a clear summary of the fix. - Transition to Review: Once the PR is successfully opened, move the Jira ticket status to "In Review".
- No Jira Comments: DO NOT post any comments on the Jira ticket at any step of this workflow. Only update ticket statuses.
Execution & Final Output
Complete the full cycle (Steps 1–6) for one ticket before starting the next. Once all Rework tickets are processed, output a concise summary table:
| Ticket Key | Root Cause Found | PR Link | Final Jira Status |
|---|---|---|---|
0 comments
Log in to comment.