> For the complete documentation index, see [llms.txt](https://engineering.umh.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://engineering.umh.app/engineering/development-process/how-to-build/tickets.md). # Tickets Which tickets we use, how they hang together, and where a new issue goes. Owner: Jeremy Every issue in Linear sits under a home ticket: a rollout ticket or a monitoring ticket. That way every problem has an owner who knows the feature. ## Rules * Every rollout and monitoring ticket has at least these three sub-tickets: Security, Bugs and Tech debt. * An issue that fits more than one goes under the first that fits: Security, then Bugs, then Tech debt. * The owner of the home ticket owns every issue under it. * Whoever files an issue and finds the sub-ticket missing creates it. * One ticket can cover several repositories. Each repository gets its own sub-ticket, so the parent closes only when all of them do. * Every ticket is one of three things: a home ticket, a [signal](/engineering/development-process/how-to-decide-what-to-build/signals.md), or work a spec describes. * A ticket carries the name other people already use for what it is about. * A ticket's state says whether anyone is expected to act on it. ## The tickets * [Rollout](/engineering/development-process/how-to-build/tickets/rollout.md): a [pitched](/engineering/development-process/how-to-decide-what-to-build.md#rollout-tickets) piece of work with one owner. * [Monitoring](/engineering/development-process/how-to-build/tickets/monitoring.md): the permanent home of a feature area, one per Product Owner area. When a rollout ticket is done, new issues go here, and new rollout tickets are cut out of it. * [Bugs](/engineering/development-process/how-to-build/tickets/bugs.md): something a user can run into today. * [Tech debt](/engineering/development-process/how-to-build/tickets/tech-debt.md): a problem that only a future change to the code can trigger. * [Security](/engineering/development-process/how-to-build/tickets/security.md): a potential security issue, whether it is exploitable today or not. ## The ticket state **Ideas means nobody is expected to act on the ticket yet.** It is a [signal](/engineering/development-process/how-to-decide-what-to-build/signals.md), or work nobody has accepted. **Todo means it has been accepted and someone is expected to pick it up.** The states after that say who is working on it. ## Public names **A concrete problem often has an identifier the whole industry uses, like a** [**CVE**](/engineering/development-process/how-to-build/tickets/security.md). A kind of problem has a name for the class, like a [CWE or an OWASP entry](/engineering/development-process/how-to-build/tickets/security.md). A part of our product has the name customers and our documentation use, like Bridges. An idea from a book we follow has the book's own term, like [the end-to-end argument](/engineering/development-process/how-to-build/coding-standards/architecture/data-integrity.md). **When two tools report the same CVE, they have found the same flaw.** **A CWE names a class of problem.** Anyone can look it up and read how others fix it, and ask what else of that kind we have. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://engineering.umh.app/engineering/development-process/how-to-build/tickets.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.