Jira Bug Report Quality Score and Rewrite Guide
Score a Jira bug report from 1 to 5 on reproducibility, evidence and clarity, then get a rewritten version and tips to help reporters improve.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[ADD STEP] [ADD VERSION] [ADD EVIDENCE] is an editorial flag, not a blank to fill. Replace or resolve each flag before you use the result.
Score and improve this Jira bug report. The report as written: [BUG_REPORT_TEXT]. The product and the area affected: [PRODUCT_AND_AREA]. What the developer team told me they usually need: [DEVELOPER_NEEDS]. The reporter's role (support, tester, customer, colleague): [REPORTER_ROLE]. Score from 1 to 5 each of these: Summary clarity, Reproduction steps, Environment detail, Expected versus actual, Evidence attached, Impact and severity, Tone and neutrality. Display a table with columns Area, Score, Evidence from the text (quote it), What to add. Show the total out of 35 and a label: Developer ready, Needs info, Cannot act. Next, produce: 1. A rewritten report using only information in the original; mark gaps as [ADD STEP], [ADD VERSION] or [ADD EVIDENCE]. 2. A list of questions to ask the reporter, no more than five, in a friendly tone. 3. A reusable one-page guide titled "How to write a bug report that gets fixed" for [REPORTER_ROLE], with a 7 point checklist. Do not invent technical details or guess causes. Do not blame the reporter; frame feedback as help. Add a worked example with invented figures: a report scoring 3, 2, 1, 3, 1, 2 and 4, with the total and label.
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.