A way to record, plan and communicate a piece of work. A ticket can also be called an issue, and can be of different types such as Task, Bug, Story and Epic.
Many teams also create custom types of tickets that are relevant for their domain or project. For example, when integrating Test Case Management tools into other work planning tools, you might have types such as Test Case, Test Set and Test Execution.
Tickets are often linked either with flat or hierarchical relationships. For example many Stories may belong to an Epic, or a Test Case may Test one or more Stories. Some more generic relationships simply use "related", without specifying the type of relationship. Other relationships might indicate project planning, such as Blocks, or Do After.
Tickets typically have at least:
Many teams also create custom types of tickets that are relevant for their domain or project. For example, when integrating Test Case Management tools into other work planning tools, you might have types such as Test Case, Test Set and Test Execution.
Tickets are often linked either with flat or hierarchical relationships. For example many Stories may belong to an Epic, or a Test Case may Test one or more Stories. Some more generic relationships simply use "related", without specifying the type of relationship. Other relationships might indicate project planning, such as Blocks, or Do After.
Tickets typically have at least:
- A title or summary
- Description
- Status
There are many other fields a ticket might have, depending on the tool, configuration, domain or project.
As a ticket is worked on, it can move though various states, depending on the tools used and their configurations, these state transitions may be gated. For example, you may set it up so tickets in the "To do" status can only transition into "Cancelled" or "In progress". You might also have rules, so certain fields are required to allow a state transition.
Some tools allow automations, for example connecting CI systems to ticket management systems, so when a branch is made that refers to the ID of a ticket, the two are linked, so you can see code changes made as part of that ticket. Many other integrations and automations exist.
As a ticket is worked on, it can move though various states, depending on the tools used and their configurations, these state transitions may be gated. For example, you may set it up so tickets in the "To do" status can only transition into "Cancelled" or "In progress". You might also have rules, so certain fields are required to allow a state transition.
Some tools allow automations, for example connecting CI systems to ticket management systems, so when a branch is made that refers to the ID of a ticket, the two are linked, so you can see code changes made as part of that ticket. Many other integrations and automations exist.
