Jira Support Ticket to Product Backlog Item Conversion
Turn customer issues into good backlog items.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Convert support tickets into Jira backlog items. Tickets with customer words, frequency and impact: [SUPPORT_TICKETS]. Product areas: [PRODUCT_AREAS]. Existing backlog titles: [EXISTING_BACKLOG]. Group tickets by underlying problem, separating the customer's request from the underlying need. For each group write a problem statement from the user's view, evidence (count of tickets and an anonymised sample quote), impact, proposed issue type, draft title, description, Given/When/Then acceptance criteria, and a priority suggestion with reasons for the product owner to decide. Check for duplicates against my existing titles and link rather than duplicate. Remove personal data from examples. Share of tickets: 24 of 180 is 13.3 percent. Worked example: 24 tickets about 'cannot export invoices to PDF' from 18 customers, 6 on the largest plan; draft title 'Customers can download invoices as PDF'. Add the feedback loop: link the tickets to the backlog item, and on release notify the customers who raised it (message: what changed, and thanks) and update macros and help articles. Measures: the top-five-theme share of tickets before and after a fix (for example 13 percent falling to 4), and time from the third ticket on a theme to a backlog item. Give the support team a template for raising issues from tickets and a 30-minute monthly meeting between support and product. Fields differ by edition, so mark anything unconfirmed [VERIFY].
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.