#linear no invented severity

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.

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.