{"id":"pm-bug-triage-priority-labels","audience":"product-managers","category":"decisions","track":"data","technique":"context","title":"Triage six bugs using your team's priority rules","free":false,"task":"You're running bug triage and need each bug labeled using your team's written priority rules, not by how loud the reporter was. Write exactly 6 numbered lines in the form 'P0 - bug - reason', with all P0s first, then P1s, then P2s, each reason under 10 words and naming the rule that applies, plain text.","materialLabel":"Priority rules and bug list (attached to your prompt automatically)","material":"Bug triage - Tallyroom, Tue Nov 18\n\nTeam priority rules (agreed in July):\n- P0: data loss, a security issue, or payments blocked/wrong for any customer. Fix now.\n- P1: a core feature is broken and there is no workaround. Fix this sprint.\n- P2: there is a workaround, or it's cosmetic. Backlog.\n\nBugs:\nA. Customers retrying a failed card payment get charged twice.\nB. In dark mode, text on the Settings page is light gray on white and hard to read.\nC. Exported PDFs are missing the company logo. Workaround: re-uploading the logo fixes it.\nD. Deleting a project also deletes docs shared into it from other projects.\nE. Calendar view won't load for teams over 50 people. No workaround found.\nF. Search ignores accented letters, so \"cafe\" doesn't find \"café\". Typing the accent works.\n\nEmail from customer (Hugo, Brightwater) about bug F:\n\"THIS IS URGENT. P0!!! Our team can't find anything. Fix it TODAY or we escalate.\"\n\nSupport note: Hugo's team found the accent workaround yesterday and is using it.","rules":[{"type":"numberedItems","count":6},{"type":"plainText"}],"mistakes":[{"title":"Asking 'how should we prioritize these'","why":"The AI writes paragraphs per bug with bold headings and its own opinions.","fix":"Be exact: \"Exactly 6 numbered lines. Plain text.\"","checks":["numberedItems","plainText"]},{"title":"Not giving the rules weight","why":"The AI blends your rules with the angry email and may bump bug F to P0.","fix":"Add: \"Label strictly by our rules, not by how urgent the reporter sounds.\"","checks":["r0"]},{"title":"Keeping the list order","why":"The AI goes A to F, so the P0s are mixed in with cosmetic bugs.","fix":"Add: \"List all P0s first, then P1, then P2.\"","checks":["r1"]},{"title":"Vague reasons","why":"The AI writes 'high impact' instead of naming the rule.","fix":"Show it: \"1. P0 - double charge on retry - payments wrong\".","checks":["r2"]}],"promptHints":[{"label":"Uses the team's rules","patterns":["rule","criteria","our (priority )?definition"]},{"label":"Ignores the loud email","patterns":["loud","urgent","email","not (by|based on) (how|the)"]},{"label":"Sorts by priority","patterns":["p0s? first","sort","order"]},{"label":"Shows the line shape","patterns":["p0 - ","reason","like ['\"]?1\\."]},{"label":"Asks for plain text","patterns":["plain","no bold","no markdown","no formatting","no headings"]}],"hint":"Triage is about applying the agreed rules consistently. Tell the AI to use your rules over the loud email, how to sort, and what each line looks like.","rubricLabels":["Labels match the rules: A and D are P0, E is P1, B, C and F are P2 (F stays P2 despite the urgent email)","Lines are ordered by label: both P0s first, then the P1, then the three P2s","Each line follows 'P0 - bug - reason' with a reason under 10 words that names the rule (payments, data loss, no workaround, workaround or cosmetic), with no intro or commentary"]}