Ticket Standards
Ticket Standards are your company-wide rules for how tickets are written — one format for titles, one structure for descriptions, applying to every ticket type in every project. They exist so a board reads as one system rather than a dozen personal styles, and so KAMI AI can fix any ticket to standard with one click.
Where: Settings › Ticket Standards
The title standard
Set the format every title should follow — for example Module | Feature - Task — and an example of it done right, like Tasks | Settings - Create new user list.
The page shows a live preview of what KAMI AI would do with it: a title like "fix the emails not sending sometimes??" comes out restructured onto your pattern. The AI maps the ticket onto the format — it never invents modules or features that aren't in the ticket. If the information isn't there, the fix can only go so far, which is precisely the nudge the author needs.
The description standard
Write the description rules the way you'd brief a new hire — for example: every description has Context, What to do, and Done when sections. Plain sentences, not a schema. KAMI AI reads them the same way a person would.
Where the standards bite
On every ticket, the editor offers Fix title to standard and Fix description to standard — one click, and the AI rewrites the ticket onto your format. The standards are also what Generate from title and the other AI drafting actions aim at, so new descriptions come out in your structure from the start. See Creating and editing tickets.
Writing standards that work
- Standardise the shape, not the prose.
Epic | Feature - Taskplus three required sections is enforceable; "titles should be clear and helpful" is a wish. - Give a real example. The example teaches more than the format string — make it a genuinely good ticket from your own backlog.
- Short enough to remember. If the standard needs its own manual, people will not follow it and the AI will be fixing every ticket forever.