Structuring issues
There are several ways to structure issues in Tracker. You can apply them individually or use several at the same time.
Issue types
Your queue may include multiple issue types with different pipelines. For instance, the Basic development model
queue template includes the following issue types by default: Task
, Improvement
, Bug
, and Release
.
You can also add new issue types and set up a dedicated workflow for them if needed, such as setting up their possible statuses and status transition rules.
Links
In Tracker, you can link issues to each other. A list of clickable issue links is displayed on the issue pages. Here is what issue links let you do:
-
Decompose your issues. Break larger project chunks into standalone issues and sub-issues.
Let's say you need to implement a new feature in your product, which implies resolving multiple smaller issues. For such cases, you can create a parent issue of the
New feature
type and link sub-issues to it. -
Display issue hierarchy. Useful if the issue can only be solved after first dealing with the blocker issue.
-
Add links to issues sharing a common theme.
Components
Components help you group issues in a queue that relate to the same topic. When managing issues with components, you can set up a default assignee and access rights.
Versions
Versions help you group issues within the same queue based on the product version they belong to.
Projects
Use projects to group issues with a common deadline and responsible employee. Projects can include issues from different queues.