How Tracker works

In this section you will learn all about how Tracker works and how you can use it to suit your workflow.

You may need to set up Tracker first, which you can learn about in Setting up Tracker.

  1. Tracker structure
  2. Organizing your workflow in Tracker
  3. How to group and organize issues
  4. Planning your workload
  5. Monitoring results

Tracker structure

Organizing your workflow in Tracker requires managing two crucial elements: issues and queues. Issues describe tasks that need to be completed, while a queue sets the rules all issues within must abide by.

There are other optional elements, such as components, issue boards, and dashboards, which help users manage issues, track their status, and monitor results. You can find an overview of all these features below.


To manage your team's workload via Tracker, you need to break it down into smaller chunks called issues. Such issues may include adding a new feature to your app, managing a support service request from a client, creating a new logo, or applying for a business trip.

Each issue has its own name, assignee, deadline, and other parameters. Issues can be interlinked or form a hierarchy relative to each other.

If you want to give your employee a task to do, create an issue and make them an assignee.


Queues unify issues that share a common theme (be it a process, product, and so on) and let users configure the workflow for the issues. Each queue can have its own issue completion stages, rules for automatic issue processing, and access rights to issues.

As a rule, each team has their own workflow, so we recommend creating standalone queries for each team or company division. You can create a queue for your development department, design team, or legal department. This will turn a queue into an issue feed for a particular team. As an example, you should create an issue in the designers' queue if you need to design a new logo.

Organizing your workflow in Tracker

Issues are generally completed in multiple stages. For example, creation, resolution, review, and completion.

In Tracker, each issue stage corresponds to a certain status. Those include "Open", "In Progress", "Testing", and "Closed". To set your pipeline up around Tracker, you need to configure your workflow, which is a set of statuses an issue goes through from creation to completion as well as specific rules of transitioning between those statuses.

Your workflow is connected with your issue queue. If you need to set up multiple workflows for different teams, you can create standalone queues for each of them. You can also add multiple issue types to a single queue, and set up an exclusive workflow for each type.

Tracker also includes queue templates with preset workflows tailored for various processes to help you get started. Here's what a versatile workflow looks like:

You can create unique workflows tailored for specific issues. Try not to overload them with needless statuses. The simpler a workflow is, the easier it is to work with.

In addition to setting up workflows, you can also use queues to configure access rights to issues, automated issue processing, Mail and Yandex Forms integration, and other things. These features will allow you to tailor queues to the needs of your team.

For some examples on how you can set up workflows in Tracker, see the following sections:

How to group and organize issues

Grouping issues can prove useful for determining your workload at various stages of the project or for indicating responsibilities of your various teams or individual employees.

You can use Tracker to group issues by the following criteria:

  • Components help you group issues that share a theme into a single queue. When managing issues with components, you can set up a default assignee and access rights.

    For example, you can use components to group support service requests.

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

    For example, to schedule a bug fix for a specific product release, you can specify the product's version in the To fix in version field.

  • A tag is a type of label that can be added manually to any issue. Tags let users group issues based on any attribute, which makes it easy to search for those issues by tag later. To add tags to an issue, edit the Tags setting.

Planning your workload

There are multiple ways to plan your workload in Tracker:

Creating projects

A project can include any type of job with fixed goals and deadlines.

Use projects in Tracker to combine issues that have a shared goal that needs to be completed in the allotted deadline. You can set a deadline and assign a responsible employee for any project. Projects can include issues from different queues.

Decomposing issues

Use issue decomposition to determine the workload that needs to be sorted out for a project to be completed or for a new version of a product to be released.

Issue decomposition means breaking down larger chunks of a project into standalone issues and sub-issues. If your workload is divided into smaller, singular issues, it becomes much easier to gauge their difficulty, distribute issues among your employees and plan your deadlines. Tracker lets you decompose tasks using links. 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 feautre” type and link your sub-issues to it.

Dividing your workload into sprints

If you are engaged in long-term development of a product or project and no concrete total workload or final deadline can be estimated, you can use sprints to plan your workload instead.

In Scrum, sprints are small iterative cycles of development that last 1 to 4 weeks. When the sprints starts, your team assesses the complexity of issues stored in the backlog and selects the issues to be completed within the current sprint. Short iterative cycles make it easier to accurately gauge deadlines and change your priorities on the fly if necessary.

To use this planning strategy, first create a “Scrum” issue board. This board will let you manage sprints, rate issues using poker planning, and view the burndown chart.

Planning deadlines via the Gantt chart

You can use the Gantt chart to plan and monitor deadlines for multiple issues on a single page. This can be helpful if you want issues to be solved in a specific order or if one employee is responsible for multiple issues.

You can create a Gantt chart for a project, your queue, or a filtered issue list. The start and end dates for your issue or project are displayed as horizontal lines and can be set or edited right on the chart.

Monitoring results

Tracker offers several tools which let users view all issue-related data quickly and easily, monitor progress, and keep track of results.


A dashboard is a page that helps users monitor the status of important issues and view statistics. You can customize your dashboard and add widgets that display data you wish to track. Widgets receive issue-related data automatically and display it as issue lists, tables, or charts.

You can go to Collect request statistics to find an example on how to set up a dashboard.

Issue boards

You can easily monitor issues assigned to your team via the issue board. Issues are displayed on the board as cards with general issue parameters on them. The cards are arranged in columns that correspond to issue statuses.

A board can be used to any kind of work, not necessarily related to software development. If you're using Scrum or Kanban methodologies, try using a basic board.

Subscriptions and notifications

Tracker sends you notifications about issue changes by default. You can configure the list of events that you want to get notifications for.

You can subscribe to notifications to avoid missing any updates in a queue, component, or issues of other users.

Search for issues

You can use filters to find issues by any parameters or their combinations.

Tracker includes system filters that help you find your issues.

If you often need to search issues with specific parameters, you can create and save a custom filter. For example, you can use custom filters to find all issues in queues where you have the author or assignee status.