⚡ Productivity
Linear Issue and Project Template from a Bug Report
Turn a bug report into a Linear issue plus a project template. No invented teams, cycles, or severity scores.
0Reviews
Prompt
Act as a product engineer writing Linear (linear.app 2026) issue and project templates. You convert a pasted bug report into Linear fields. You do not invent a team key, cycle, estimate, or severity that is not in Inputs. This is not Jira and not GitHub Issues. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Team key and workspace I may use: [Team] - Bug report paste: [Bug] - Severity scale we actually use: [Sev] - Project name if this is a project, or NONE: [Project] - Labels I may apply: [Labels] - Repro environment I can prove: [Env] - Assignee I may name (or UNASSIGNED): [Assignee] - Cycle or none: [Cycle] - Words I must not use: [Banned] - Estimate scale I may use (or NONE): [Estimate] Generate: 1. Tool lock: Linear 2026. Not Jira. Not GitHub Issues. 2. Honesty ledger: team, labels, severity values, cycle, estimate, assignee, env facts from Inputs and Bug. 3. Issue title (60 chars) from Bug. Print count. No panic words from Banned. 4. Issue body: summary, repro from Env, expected vs actual from Bug, missing facts as NOT IN INPUTS. 5. Fields: team key, labels (only Labels), severity only if it matches Sev, assignee or UNASSIGNED, cycle or none. 6. Project template: if Project is NONE, skip. Else milestones that Bug actually implies, no extra epics. 7. Acceptance criteria: testable lines from Bug only. 8. Compliance pass: quote Banned, invented story points, and fake customers. Cut them. Constraints: - Linear field names. Do not emit Jira YAML. - Never invent a team, cycle, or estimate. - If Sev does not include a value, do not set priority. - Do not add screenshots you were not given. - No PII beyond what Bug already contains. Do not expand names.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Team: MOBI Bug: iOS 18.5 checkout button stays disabled after Apple Pay sheet cancel. Repro: cart 2 items, tap Apple Pay, swipe down to cancel, button remains disabled until kill app. Expected: button re-enables. Started 2026-08-18. No crash log attached. Sev: P1 P2 P3. User called it P2. We do not use S0. Project: NONE this is a single issue Labels: ios, checkout, apple-pay Env: iPhone 15, iOS 18.5, app 6.4.1 TestFlight Assignee: UNASSIGNED Cycle: none named Banned: Sev-0, millions of users, P0 Estimate: NONE we do not point bugs
Example Output
1. Lock: Linear 2026. Team MOBI. Not Jira. Not GitHub Issues. 2. Ledger: iOS 18.5; app 6.4.1 TestFlight; iPhone 15; Apple Pay cancel leaves checkout disabled; started 2026-08-18; no crash log; labels ios, checkout, apple-pay; Sev P2 allowed; assignee UNASSIGNED; cycle none; estimate NONE; project NONE. 3. Title: iOS checkout stays disabled after Apple Pay cancel (54). 4. Body: Summary from Bug. Repro: cart 2 items, Apple Pay, swipe cancel, button stays disabled until kill. Expected: re-enable. Env: iPhone 15, iOS 18.5, 6.4.1 TestFlight. Crash log NOT IN INPUTS. 5. Fields: team MOBI; labels ios, checkout, apple-pay; priority P2 (user named P2 and Sev allows it); assignee UNASSIGNED; cycle none; estimate unset. 6. Project template: skipped, Project is NONE. 7. Acceptance: after cancel, checkout button is enabled without killing the app. Do not add an Android AC. 8. Compliance: cut Sev-0, millions of users, P0. No invented points. Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.