Concepts

In this section, you'll learn about the key terms and concepts used in Yandex Tracker and this Help.

A

Agile

See Agile methodologies.

Agile methodologies

Agile methodologies are collaborative approaches where work is completed in short cycles called sprints. You can use various Agile methodologies, such as Scrum and Kanban.

Yandex Tracker brings Agile tools together on an issue board. To learn more, see Boards.

Auto action

Auto actions update or create issues in a queue automatically on a set schedule.
For example, you can configure an auto action to create an issue for data backup every week or notify an assignee if the status of their issue doesn't change.

For more information about auto actions, see Automatic issue updates in Tracker, Scheduled issue creation in Tracker

B

Backlog

A backlog is a list of issues or product requirements that must be completed in a project. Backlog issues are usually sorted by priority.

C

Checklist

Checklist is a to-do list or a list of planned issue stages that you can mark as completed. You can add checklists to issues in Yandex Tracker. To learn more, see Creating a checklist.

Component

A component is a parameter that helps you group queue issues by subject, such as product, workflow, or lead. Components can be configured on the queue page. To learn more, see Creating a component.

D

Dashboard

Dashboard is a page where you can monitor statuses of important issues and view issue statistics. You can add issue lists, tables, charts, and notes to the dashboard. Learn more about dashboards

E

Epic

In Agile methodologies, an epic is a larger feature or requirement that can't be delivered in one sprint. In Yandex Tracker, you can use an Epic issue to group any issues based on a shared subject. To learn more, see Epics.

F

Filter

In Yandex Tracker, you can use filters to search for issues by parameters. For example, you can find all issues in queues where you have the author or assignee status. To learn more, see Creating and configuring an issue filter.

G

Gantt chart

Gantt chart is a project visualization tool that shows issues as horizontal bars on a timeline so you can easily plan and track progress. Learn more about Gantt charts

Global field

A global field is an issue field that can be used across all Yandex Tracker queues. Only administrators can create global fields. To learn more, see Global fields.

Goal

A goal defines the desired outcome or result that a team has to achieve. You can use this tool to track the progress of your goals and review their key results. Learn more about goals

I

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 invited user will get a notification with the comment text by email and in Yandex Tracker Notifications (if the user has accessed the Yandex Tracker interface before).

To learn more, see Inviting to comment.

Issue

In Yandex Tracker, you can use issues to register tasks, requests, and other types of work. An issue has a name, assignee, deadline, and other parameters.

To learn more, see How to create an issue, Working with issues

Issue board

Issue boards are a tool that helps you easily monitor and update issue statuses. On the board, issues are shown as cards distributed across columns of the board depending on their status. To learn more, see Working with issues on a board.

Issue key

Issue key is a unique ID of the issue. It consists of the queue key and the sequence number, for example: TEST-123. You can use this key to access the corresponding issue via a link: https://tracker.yandex.com//TEST-123.

Issue parameters

Issue parameters are various attributes of an issue, such as Assignee, Deadline, or Status. You can edit parameters on the issue page. To learn more, see Editing issue fields.

Issue type

In Yandex Tracker, you can create various types of issues, including New Feature, Bug, and Improvement. In the queue created for each issue type, you can set up your workflow.

To learn more, see Adding an issue type to a queue.

L

Link

A link is a reference from one issue to another that shows the dependency between them. For example, when an issue is a sub-issue of another, or when completing one issue depends on the result of another. To learn more, see Links between issues.

Local field

A local field is an issue field that can be used only in a specific Yandex Tracker queue. Local fields can be created by queue owners. To learn more, see Creating a local field.

M

Macro

Macro is a set of scripted operations that you can run on the issue page. To learn more, see Setting up macros in Tracker.

O

Organization

In Yandex 360, an organization represents a company profile where you can add new employees and bring them together in divisions and groups.

P

Portfolio

In Yandex Tracker, a portfolio is a set of projects and other portfolios grouped under a single initiative. Portfolios help you structure and manage your project work. Learn more about portfolios

Project

In Yandex Tracker, a project is a set of issues that aim to achieve a common goal within a defined period. 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. Learn more about projects

Q

Queue

A queue is a space for issues that share a common workflow or focus on the same product. 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. To learn more, see Configuring queues.

Queue key

Queue key is a unique code consisting of Latin characters that helps identify the queue; for example: TEST. You can use this key to access the corresponding queue via a link: https://tracker.yandex.com//TEST. Learn more about requirements for issue keys

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.

Query language

The query language is a text-based format for writing conditions used to search for issues. Learn more about the query language

R

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). To learn more, see Resolutions in issues.

S

SLA

In Yandex Tracker, an SLA is a set of rules that define time 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.

To learn more, see Configuring an SLA for issues.

Sprint

In Agile methodologies, a sprint is an iterative project cycle that usually lasts from one to four weeks. In Yandex Tracker, you can use sprints on boards with a backlog and sprints. To learn more, see Sprints.

Status

Status is an issue attribute that shows the current progress toward issue completion. For example: "Open", "In progress", "Testing", and "Closed". To learn more, see Issue statuses, Transitions between statuses

Story

In Agile methodologies, a user story is a description of a feature or function that must be implemented in a product. In Yandex Tracker, you can use a Story issue to group any issues based on a shared subject.

Story point

Story point is a unit of effort required to complete an issue. A story point doesn't correspond to a fixed number of hours. The team rates issues collectively by comparing them to a simple task.

To learn more, see Estimating effort for issues.

T

Tag

A tag is a label that you can manually add 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 Tags parameter.

Trigger

Trigger is a set of actions on an issue that are executed automatically if certain conditions are met. To learn more, see How do I set up a trigger?.

V

Version

Version is a parameter that groups issues by product version. Version values can be configured on the queue page. To learn more, see Creating a version.

W

Widget

A widget is an information block on the dashboard that automatically pulls issue data and displays it as a list, table, or chart. Learn more about widgets

Workflow

A workflow is a 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. To learn more, see Workflows in queues.

Y

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. To learn more, see Text formatting.