Create intermediate Works with: Any AI

Triage a Jira Bug Backlog Into Fix Now, Plan, Ask and Close

Table output Has example

• 🧭 Jira

Sort a list of bugs into clear next actions with reasons.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

Triage this list of Jira bugs. The export with key, summary, severity as filed, created date, last updated, reporter type (customer, internal), number of affected users or tickets if known, and workaround noted: [BUG_LIST]. Our release dates and capacity for fixes in the next sprint: [RELEASE_AND_CAPACITY]. Our severity definitions: [SEVERITY_DEFINITIONS].

Sort each bug into one of four outcomes: Fix now (serious, affects many users, no workaround), Plan (real but not urgent), Ask (cannot be judged without more information; write the exact question), or Close (duplicate, cannot be reproduced after a request, or already fixed). Every outcome must be traceable to a number or quoted fact from the list; ask me for missing fields before guessing, and mark judgements on thin data as low confidence. Give a one-line reason citing the data and a suggested severity if it differs from the one filed. Group probable duplicates and name the one to keep. Count bugs per outcome against the total, with arithmetic, and estimate how many fit in the next sprint from the capacity I gave. Do not close anything on age alone.

Output a table with Key, Outcome, Reason, Suggested severity and Next action, then paste-ready comments under 60 words and polite: a request for more information, a duplicate closure and a stale closure. Triage proposes; the product owner decides.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Invented list of 40 bugs. Outcomes: Fix now 4, Plan 14, Ask 11, Close 11 (duplicates 6, cannot reproduce 3, fixed 2); total 40. Example row: PAY-212 'Card payment fails for amounts over 1,000', severity filed Minor, 23 customer tickets in a week, no workaround; suggested severity Major; outcome Fix now. Example Ask row: UI-87 'Button looks wrong'; question: 'Which browser and screen size, and can you attach a screenshot?' Capacity next sprint: 5 fixes, so the 4 Fix now bugs plus 1 Plan item fit. Duplicate group: PAY-190, PAY-201, PAY-205; keep PAY-190.

• jira