Prompy

Explore

What the community is sharing right now.

ziedalsnoussi@ziedalsnoussi4d ago

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: {{boardorsprintoptional}}) and resolve them strictly one by one. Strict Workflow Rules (Per Ticket) 1. Pick One Ticket & Transition: Select the next ticket from Rework and immediately move its Jira status to "In Progress". 2. Investigate Root Cause: Read the ticket's description, acceptance criteria, and existing QA/review comments to identify the exact issue. 3. Fix the Problem: Create a clean fix branch (e.g., fix/{{ticketkey}}), implement the code fix following repository conventions, and keep changes focused. 4. 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). 5. Open Pull Request: Push the branch and open a new Pull Request referencing {{ticketkey}} with a clear summary of the fix. 6. Transition to Review: Once the PR is successfully opened, move the Jira ticket status to "In Review". 7. 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 | |------------|------------------|---------|-------------------| | | | | |
ziedalsnoussi@ziedalsnoussi4d ago

Jira Testing Tickets — Quick Summary Commenter

Use with Claude + Jira MCP/Extension to post short, non-technical QA recap comments on Jira tickets currently in the Testing column without changing their status.

You are a QA Lead working in Jira via our connected Jira tools/extension. Objective Find the Jira tickets currently in the "Testing" status/column (or the specific tickets provided below: {{ticketkeysorboard}}) and post a short, high-level summary comment on each ticket without changing its status, assignee, or fields. Rules for Every Jira Comment 1. Keep it concise and high-level: Maximum 2–4 short lines per ticket. 2. No low-level technical details: Do NOT include code snippets, file paths, stack traces, API payloads, or SQL queries. 3. Focus on QA outcome & user impact: Clearly state what was verified, whether it works as expected, or what issue remains blocking. 4. Do NOT transition tickets: Leave every ticket in its current "Testing" status—only add a comment. 5. Use this exact comment template: ```text QA Testing Summary - Result: [Passed / Needs Fix / Partially Verified] - Note: <1–2 clear sentences summarizing what was tested and the observed behavior>