Concepts

In this section, you will find the basic terms and concepts used in Tracker and this Help.

A

Agile methodologies: Team work strategies that follow iterative development at their core, breaking the workload down into smaller cycles called sprints. There is a number of Agile development approaches, e.g., Scrum and Kanban. In Tracker, agile tools are grouped on issue boards.

Backlog: List of issues or product requirements that must be completed in a project. Backlog issues are usually sorted by priority.

Checklist: To-do list or list of planned issue stages that you can use to mark items you have completed. Tracker allows users to add checklists to issues.
Component: Parameter that allows users to group queue issues related to the same subject, such as their product, pipeline, responsible party, etc. Components can be configured on the queue page.

Dashboard: Page that helps users monitor the status of important issues and view statistics. You can add issue lists, tables, charts, and notes to the dashboard. Learn more about dashboards.

Epic: In Agile methodologies, an epic is a larger feature or requirement that cannot be implemented within a single sprint. Tracker includes the {{ ui-key.startrek-backend.fields.issue.epic }} issue type that can be used to group any issues by theme.

Filter: You can use filters to search for issues in Tracker by parameters. For example, you can find all issues in queues where you have the author or assignee status. More about searching issues by parameters.

Invite to comment: Inviting a user to comment means entering the user's name when sending a comment to an issue in order to draw their attention to that comment. The mentioned user will receive a notification with the text of the comment by email and in Tracker notifications (if the user opened the Tracker interface before).
Issue: In Tracker, issues can be used to register tasks, requests, and other types of work. An issue has a name, assignee, deadline, and other parameters. Learn more about creating issues and managing issues.
Issue board: Boards help users easily monitor and update issue statuses. On the board, issues are shown as cards distributed across columns of the board depending on their status. Learn more about boards.
Issue parameters: Various attributes of an issue, such as {{ ui-key.startrek-backend.fields.issue.assignee-key-value }}, {{ ui-key.startrek-backend.fields.issue.dueDate-key-value }}, {{ ui-key.startrek-backend.fields.issue.status-key-value }}, etc. You can edit parameters on the issue page.
Issue type: Tracker issues come in various types, e.g., New feature, Error, or Improvement. In the queue created for each issue type, you can set up your workflow.

Key (queue key and issue key)

Queue key is a unique code consisting of Latin characters, which can be used to identify a queue, e.g., TEST.

Issue key is a unique ID of the issue. It consists of the queue key and the sequence number, e.g., TEST-123.

Link: Reference in an issue to another one showing the hierarchy between the two. For example, when an issue is a sub-issue of another one, or completing an issue depends on the result of another issue. You can read more about issue linking here.

Project: In Tracker, projects are sets of issues that have a common goal to accomplish within a certain timeline. Every project has a deadline and a lead. Projects can include issues from different queues, so they are useful for grouping tasks that involve various teams. You can learn more about projects here.

Queue: Space for the issues being worked on under a single product or pipeline. Queues can also be used as an issue list meant for a specific team or department. Queues enable you to order your issues and see who is responsible for their execution. More about setting up queues.
Query language: Text-based format for creating conditions used for searching issues. You can learn more about our query language here.
Queue team: Queue team includes users who create and complete issues in the given queue. You can assign the team members privileged access rights to issues in the queue.

Resolution: Resolution is an issue attribute that specifies why the issue was closed. For example, an issue can be closed because it was completed (the Resolved resolution) or because it is a duplicate of another issue (the Duplicate resolution).

SLA: In Tracker, an SLA is rules that define timeframes for processing issues in queues. For example, you can set the time within which the assignee has to respond to the issue, answer the requestor's comment, or complete the issue. Learn more about SLAs.
Sprint: In Agile methodologies, a sprint is an iterative project cycle that usually lasts from one to four weeks. Tracker allows you to use sprints on Scrum issue boards.
Status: Issue attribute that shows the current state of the issue completion progress, For example: Open, In progress, {{ ui-key.startrek-backend.presets.advancedDevelopment.board.column.testing }}, and Closed.
Story: In Agile methodologies, a user story is a description of a feature that needs to be implemented in a product. Tracker includes the Story issue type that can be used to group any issues based on a common topic.
Story Point: Relative rating that describes the effort needed to complete working on an issue. A story point unit is not usually measured in terms of man-hours. The team rates issues collectively by comparing them to a simple task.

Tag: Type of label that can be added manually to any issue. You can use tags to group issues by any attribute and then search for issues with preset tags. To add tags to an issue, edit the {{ ui-key.startrek-backend.fields.issue.tags-key-value }} parameter.

Version: Parameter that allows you to group issues pertaining to the same version of a product. Version values can be configured on the queue page.

Widget: Information section located on the dashboard that automatically receives issue-related data and displays it as a list, table, or chart. You can learn more about widgets here.
Workflow: Set of possible issue statuses and rules for transitioning between them. Queue settings for issues of various types allow users to choose pre-configured workflows or create custom ones.

Yandex Flavored Markdown (YFM): Yandex Flavored Markdown markup is a set of rules for formatting text using special characters. You can use it to format text in issue descriptions and comments.