Basic concepts
In this section, you will find key terms and concepts used in Tracker and in this Help.
A
- Agile (Agile methodologies)
-
Agile methodologies are collaborative approaches where work is completed in short cycles, such as sprints. Popular Agile methodologies include Scrum and Kanban.
- Auto action
-
An auto action is a rule that updates issues in a queue or creates new ones on a schedule.
B
- Backlog
-
A backlog is a section on the board with a backlog and sprints that contains all issues that are not yet completed.
C
- Checklist
-
A checklist is a list of items within an issue. It's convenient for marking completed work steps.
- Component
-
A component is a parameter that helps you separate workflows in a queue, for example, by product or by the responsible employee. For a component, you can select individual access settings for issues.
D
- Dashboard
-
A dashboard is a page where you collect issues, metrics, and other important data. It helps you monitor information in one place without having to search through different Tracker sections.
E
- Epic
-
In Agile, an epic is a large task or requirement that cannot be completed in one sprint.
F
- Filter
-
A filter is a tool for searching for issues by conditions. For example, you can find issues in a specific queue where you are the author or assignee.
- Form
-
A form is a page with questions and fields for entering data. In Tracker, you can use a form as a template for creating issues.
G
- Gantt chart
-
A Gantt chart is a project visualization tool that shows issues as horizontal bars on a timeline so you can easily plan and track progress.
- Global field
-
A global field is an issue field created by the organization administrator. It is available in all Tracker queues.
- Goal
-
A goal is a development strategy or the desired outcome of a team's work. Goal progress is measured using quantitative indicators. You can link projects, portfolios, and issues to a goal to see what work is being done to achieve it.
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 user will receive a notification. How to invite to comment
- Issue
-
An issue in Tracker is a unit of work: a task, request, bug report, or other type of request. An issue has a name, description, status, assignee, deadlines, and other parameters.
- Issue board
-
An issue board is a visual representation of issues arranged in columns. Each column corresponds to a status, for example , , .
- Issue key
-
An issue key is a unique identifier contained in the issue link. It consists of the queue key and a number, for example
TEST-123. - Issue parameters
-
Issue parameters are fields with data about the issue that are displayed on the right panel. For example, Assignee, Deadline, Status.
- Issue type
-
A type is an issue parameter that helps you categorize issues by their purpose. For example: New Feature, Bug, Improvement. You can set up different workflows for different types.
K
- Key results
-
Key results are quantitative, time-bound indicators for a goal. They help you assess how much progress the team has made toward the goal.
L
- Link
-
A link is a formatted reference from one issue to another. It shows the dependency between issues. For example, add a Dependent issue — Blocks link if the work cannot be done until the previous stage is completed.
- Local field
-
A local field is an issue field created by an employee in the queue settings.
M
- Macro
-
A macro is a set of actions on an issue that a user runs by clicking a button on the issue page.
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
-
A portfolio is a tool for grouping projects and other portfolios by product, department, or other criteria.
When you have multiple parallel projects, a portfolio lets you view them from a high level: how resources are distributed, where deadlines are approaching.
- Project
-
A project is a set of issues from different queues where work is being done towards a common result. This could be launching a mobile app or redesigning a website's homepage.
A project helps you track: how many issues are done, how many are left, and whether the team is meeting deadlines.
- Project resources
-
Project resources are the working time of employees, allocated across issues in projects and portfolios. The resource management tool helps you plan workload and deadlines.
Q
- Query language
-
A query language is a method for searching issues where you write conditions as text. You can use it to change the order of actions or substitute dynamic values. On the issue search page, click Query language.
- Queue
-
A queue is a space for issues related to a single process, product, team, or department. A queue helps you store issues in one place and manage work according to common rules.
- Queue key
-
A queue key is a unique code for a queue consisting of Latin characters, for example
TEST. The key is contained in the link to the queue and its issues, and you need to specify it in API requests and auto action settings. You can't change the key after creating the queue. - Queue team
-
A queue team is a user category in the queue settings. Add employees who work on the queue's issues most often.
When you assign assignees or invite someone to comment, Tracker will suggest these people in the tooltip. The selected employees will also see the queue in their workspace under the My queues filter.
R
- Repository
-
A repository is a project's source code storage. Tracker supports integration with repositories on GitHub, GitLab, and Bitbucket.
- Resolution
-
A resolution is an issue parameter that shows why an issue was closed. For example: Resolved, Won't fix, or Duplicate. You can add resolutions in the queue settings.
- Robot
-
A robot is a service account that Tracker uses to perform automated actions in issues.
S
- SLA
-
An SLA is a time frame within which an issue in a queue must be processed. If the time frame is exceeded, the timer owner receives a notification.
- Sprint
-
A sprint is a short work cycle in Agile, usually lasting 1–4 weeks. In Tracker, sprints are used on boards with backlogs and sprints.
- Status
-
A status is an issue parameter that shows the current stage of the issue. For example , , .
- Story
-
A user story is a description of a feature or capability from the user's perspective. In Tracker, the Story issue type can be used to group issues with a common theme.
- Story Point
-
A story point is an estimate of the relative complexity of issues. Each team defines its own way of estimating issue effort. You need to specify the estimate on the issue page.
T
- Tag
-
A tag is a label that helps you group issues by some other attribute. Using a tag, you can quickly find these issues in search. A tag is created on the issue page, in the Tags parameter.
- Token
-
A token is a secret key for accessing the API. It authenticates the user or application, so it must not be shared with others.
- Trigger
-
A trigger is an automated rule. It performs actions on an issue when specified conditions are met.
V
- Version
-
A version is a parameter that groups queue issues by product version. You can add versions in the queue settings.
W
- Webhook
-
A webhook is a notification that one service sends to another via an HTTP request when a specific event occurs. For example, a repository can send Tracker data about new commits.
- Widget
-
A widget is a card with text, a table, or a chart that you can add to a dashboard.
- Workflow
-
A workflow is a set of issue statuses and rules for transitioning between them. You can set up multiple workflows in each queue.
Y
- Yandex Flavored Markdown (YFM)
-
Yandex Flavored Markdown (YFM) is a set of rules for formatting text using special characters. You can use it in issue descriptions and comments.