jira-ticket-writinglisted

# Jira Ticket Writing The formula for tickets humans can read in ~15 seconds. The what and why go at the top; the how and evidence go in a comment. One Story per brief or theme; consolidate rather than inflate. ## Core principle A Story is readable by a non-technical stakeholder in 15 seconds. This means: plain English, active voice, value-oriented title, high-level description. All implementation detail and verification evidence lands in the first comment -- never in the description -- so the description reads clean. ## Story template **Title:** verb + outcome, plain English, no jargon, 80 chars max. **Description fields:** | Field | Content | |-------|---------| | *Objective* | 1-2 sentences: what it achieves and why (high level). | | *What it covers* | 3-5 bullets of scope -- what, not how. | | *Acceptance criteria* | Checklist "Done when..." -- verifiable, not vague. | | *Links* | Brief slug / repo if applicable. | **Evidence** -- first comment only, never in description: commit hashes, verbatim commands, anything reproducible. ## Subtask template **Title:** short action phrase, plain English. **Description:** one line -- what it is / done when X. ## Process 1. **Map to a brief or theme.** One Story = one brief or coherent chunk of work. If the work spans multiple unrelated concerns, split into separate Stories. If it is one theme with sequential steps, use Subtasks. 2. **Write the title last.** Draft the Objective and What-it-covers first; the title