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 You need: project admin rights
When to use this, and when not to
| You want | Use |
|---|---|
| Every ticket written the same way | Ticket Standards |
| A reusable ticket you create repeatedly | A template |
| Different workflows per project | Custom statuses |
| Help writing one specific ticket | The AI actions on the ticket itself |
Standards are company-wide and apply to every ticket type, so they describe shape rather than content. Anything that varies by project belongs in project settings instead.
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 are not in the ticket. If the information is not 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 would 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 as a person would.
Where the standards bite
On every ticket the editor offers Fix title to standard and Fix description to standard — one click to rewrite onto your format. The standards also aim the other AI actions, including Generate from title, so new descriptions come out in your structure from the start. See Creating and editing tickets.
What Happens Next
- The standard applies from the moment you save it, to the AI actions on every ticket.
- Existing tickets are not rewritten. Nothing is retrospective; old tickets stay as they are until someone presses the fix button on them.
- A changed standard changes what the fix buttons produce from then on.
Tips
- 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, from your own backlog. The example teaches more than the format string.
- 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.
- Roll it out with the fix button, not with a memo. Ask people to press "fix to standard" on tickets they touch; the backlog converges without anyone rewriting history.
- Revisit once, after a month. The first standard is always slightly wrong in a way only real use reveals.
Troubleshooting / FAQ
Q: The AI fix produces a vague title. The ticket does not contain the information the format asks for. It maps what is there onto your pattern; it does not invent modules.
Q: Old tickets still look inconsistent. Standards are not retrospective. Use the fix buttons as tickets get touched.
Q: The standard is being ignored. Usually it is too long or too abstract to hold in the head. Shorten it to something someone can follow without looking it up.