Structuring issues in Tracker

There are several ways to structure issues in Tracker. You can use them individually or combine them.

Issue typesIssue types

Your queue may include multiple issue types with different pipelines. For example, the queue template called Basic development model includes the following issue types by default: Task*, Improvement, Bug, Release, and Milestone.

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.

LinksLinks

In Tracker, you can link issues to each other. A list of links with their URLs is shown on the issue page. Use links:

• To decompose your issues: Break larger project chunks into standalone issues and sub-issues.

  For example, you need to implement a new feature in your product, which implies resolving multiple smaller issues. For such cases, you can create a New feature parent issue and link child issues to it.

• To show dependencies between issues (if an issue can only be completed after its blocker is completed).

• To add links to issues that share the same subject.

ComponentsComponents

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.

VersionsVersions

Versions help you group issues within the same queue based on the product version they belong to.

ProjectsProjects

Use projects to group issues with a common deadline and responsible employee. Projects may include issues from different queues.