⚡ Productivity
Jira Issue Template from a Workflow Brief (No Invented Assignees)
Build a Jira issue template from a workflow brief. Never invent assignees, sprint IDs, or unlisted custom fields.
0Reviews
Prompt
Act as a Jira issue template writer who only uses a pasted workflow brief. You emit issue type, summary pattern, description sections, and required fields. You do not invent assignees, sprint IDs, or custom fields. This is not a Linear template, not a GitHub issue form, and not a standup bot. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow brief (types, statuses, required questions): [Brief] - Project key I lock (or NONE): [Key] - Custom fields I may list (exact names or NONE): [Fields] - Assignee policy: [Assignees or NONE] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Max sections: [Max] Generate: 1. Honesty ledger: Brief items, Key status, Fields status, Assignees policy, Lang, Max. Forbidden: invented people, invented sprints. 2. Type map: issue types and statuses from Brief or NOT IN INPUTS. 3. Template: summary pattern, description sections up to Max, required questions from Brief. Assignee line only if Assignees not NONE. 4. Field list: only Fields names; if Fields NONE print custom fields NOT IN INPUTS. 5. Refuse list: invented emails, invented story points, invented sprint names. 6. Diff notes: Banned/Never cuts. 7. Key note: if Key NONE, leave project key as NOT IN INPUTS. 8. Compliance pass: Banned/Never hits. Section count vs Max. Gaps list of five. Format as Format. Constraints: - Jira template from Brief only. Not Linear and not a GitHub issue form. - Never invent assignees, sprint IDs, or unlisted custom fields. - Stay at or under Max sections. - No emojis.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Brief: Bug type. Statuses: To Do, In Progress, Done. Required questions: steps to reproduce, expected, actual, environment. Definition of done: tests updated if a test file is named in the ticket. Key: MESH Fields: Environment, Repro Rate Assignees: NONE Banned: rockstar, ASAP hero, guaranteed SLA Never: invent assignees, invent sprint IDs, invent story points, invent components Format: ledger + map + template + fields + refuse + diff + key-note + gaps Lang: English Max: 4
Example Output
1. Ledger. Brief: Bug; statuses To Do, In Progress, Done; questions steps/expected/actual/environment; DoD tests updated if a test file is named. Key MESH. Fields Environment, Repro Rate. Assignees NONE. Lang English. Max 4. Forbidden: invented people, sprints, rockstar, ASAP hero, guaranteed SLA. 2. Map. Type Bug. Statuses To Do / In Progress / Done. Components NOT IN INPUTS. Sprint NOT IN INPUTS. 3. Template. Issue type: Bug Summary pattern: [MESH] <short failure> Description sections (4): 1. Steps to reproduce 2. Expected 3. Actual 4. Environment Definition of done: tests updated if a test file is named in the ticket. Assignee: NOT IN INPUTS 4. Fields. Environment. Repro Rate. No other custom fields. 5. Refuse. Assignee emails: refused. Sprint MESH-S12: refused. Story points: refused. Component Mesh-Core: refused. 6. Diff. Cut rockstar / ASAP hero / guaranteed SLA if attempted in description. 7. Key. MESH locked. Project key printed as MESH. No second project invented. 8. Compliance. Banned hits none. Sections 4 vs Max 4. Format ledger+map+template+fields+refuse+diff+key-note+gaps. Gaps: priority values, label list, repro-rate allowed values, linked-issue types, attachment policy. 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.