In this section, you'll find the basic terms and concepts used in Tracker and this Help.
- Agile methodologies
- Team work strategies that follow iterative development at their core, breaking the workload down into smaller cycles called sprints. There are several variations of agile methodologies, such as Scrum and Kanban. In Tracker, agile tools are grouped on the issue board.
- A list of issues or product requirements that must be completed in the project. Backlog issues are usually sorted by priority.
- A checklist is a to-do list or a list of planned issue stages that lets you mark items you've completed. Tracker lets users add checklists to issues.
- A parameter that lets users group queue issues based on a shared theme, such as their product, process, responsible party, and so on. Components can be configured on the queue page.
- A dashboard is a page that helps users monitor the status of important issues and view statistics. A dashboard can display lists, tables, graphs, and notes. Learn more about dashboards.
- In Agile methodologies, an epic is a larger feature or requirement that can't be implemented within a single sprint. Tracker includes the Epic issue type that can be used to group any issues based on a shared theme.
- Filters let users search for issues in Tracker by issue settings. This can be used to find all issues in queues where you have the author or assignee status, among other things. Learn more about using filters.
- Invite to comment
- Inviting a user to comment means entering that user's name when sending a comment to an issue in order to draw their attention to that comment. The selected user will receive an email notification with the comment in question.
- In Tracker, issues can be used to register tasks, requests, and other types of work. Each issue has its own name, assignee, deadline, and other parameters. Learn more about creating issues and working with issues.
- Issue board
- Boards help users easily monitor and update issue statuses. Issues are displayed on the board as cards, which are sorted into columns based on their status. Learn more about issue boards.
- Issue fields
- Issue fields are various attributes such as an issue's
Status, and so on. Fields can be edited on the issue page.
- Issue type
- There are various types of Tracker issues, such as
Improvement. You can customize your workflow for queues of each issue type.
- Key (queue and issue)
The queue key is a unique code comprised of Latin characters that can be used to identify a queue. For example:
An issue key is a unique issue ID. It's comprised of a queue key and and an issue index. For example:
- An issue link means a link included in an issue that refers to another issue and shows the hierarchy between the two. Such as when one issue is considered a parent issue. Or when completion of an issue depends on the results of another issue. Learn more about issue links.
- Organization refers to the company account. Company employees receive access to platforms featured on Yandex.Cloud in order to work together.
- In Tracker, projects are sets of issues that have a shared goal. Projects have deadlines and responsible employees. A project may include issues from multiple queues, which is why they're convenient for grouping issues meant for different teams. Learn more about projects.
- Query language
- A query language is a text-based format for entering conditions used for searching issues. Learn more about the query language.
- A queue is a common workspace for issues in the same pipeline or for a single product. Queues can also be used as a list of issues meant for a specific team or department. Queues help you organize issues and quickly find their assignees. Learn more about queue settings.
- A resolution is an issue attribute that specifies why the issue was closed. For example, an issue can be closed because it was completed (the
Resolvedresolution status) or because it's a duplicate of another issue (the
- In Tracker, an SLA is a set of rules that defines a timeframe for processing issues in the queue. For example you can set up a time limit during which the assignee must respond to a new issue, respond to a client's comment or completely finish their work on the issue. Learn more about using SLAs.
- In Agile methodologies, a sprint is an iterative project cycle that usually lasts from 1 to 4 weeks. Tracker lets you use sprints on
- A status is an issue attribute that reflects the current state of the issue completion process. For example:
- In Agile methodologies, a
User Storyis a description of a feature or function that needs to be implemented in the product. Tracker includes the Story issue type that can be used to group issues based on a shared theme.
- Story Point
- A relative rating that describes effort needed to complete an issue. Usually a story point doesn't directly correlate with the number of work hours needed to solve the problem. The team rates issues collectively by comparing them to a simple task.
- 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 parameter.
- A parameter that lets you group issues pertaining to the same version of a product. Version values can be configured on the queue page.
- An information block located on the dashboard that automatically receives issue-related data and displays it as a list, table, or chart. Learn more about widgets.
- Wiki markup
- The Wiki markup is a set of rules for formatting text using special characters. You can use it to format the text in issue descriptions and comments.
- A set of possible issue statuses and status transition rules. The queue settings for issues of various types let users choose preset workflows and create custom ones.