Jira tracks issues, which can be bugs, feature requests, or any other tasks you want to track.

Each issue has a variety of associated information including:

  • the issue type
  • a summary
  • a description of the issue
  • the project which the issue belongs to
  • components within a project which are associated with this issue
  • versions of the project which are affected by this issue
  • versions of the project which will resolve the issue
  • the environment in which it occurs
  • a priority for being fixed
  • an assigned developer to work on the task
  • a reporter - the user who entered the issue into the system
  • the current status of the issue
  • a full history log of all field changes that have occurred
  • a comment trail added by users
  • if the issue is resolved - the resolution

Issue Types

Jira can be used to track many different types of issues. The currently defined issue types are listed below. In addition, you can add more in the administration section.

For Regular Issues
Story
Created by Jira Software - do not edit or delete. Issue type for a user story.
Epic
Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.
Task
A task that needs to be done.
Sub-task
The sub-task of the issue
Bug
A problem which impairs or prevents the functions of the product.
Daily
For Sub-Task Issues
Buffer
Тип карточек под Ганта, не имеет смысла, кроме визуально отображать буффер в ганте
Sub-Template
Sub-Issue Type for Templates
Sub-task
The sub-task of the issue
Sub-bug
The Sub-bug of the issue.Использовать для незаконченных работ, как указатель на недоделку. Багом может стать после релиза/влития работы в основной билд

Priority Levels

An issue has a priority level which indicates its importance. The currently defined priorities are listed below. In addition, you can add more priority levels in the administration section.

high
Serious problem that could block progress.
Blocker
Эта проблема может остановить прогресс.
normal
Has the potential to affect progress.
low-
Trivial problem with little or no impact on progress.
high+
This problem will block progress.
low
Minor problem or easily worked around.

Statuses

Status Categories

Helps identify where an issue is in its lifecycle.
Issues move from To Do to In Progress when work starts on them, and later move to Done when all work is complete.

Done

Represents anything for which work has been completed

In Progress

Represents anything in the process of being worked on

No Category

A category is yet to be set for this status

To Do

Represents anything new

Issue Statuses

Each issue has a status, which indicates the stage of the issue. In the default workflow, issues start as being Open, progressing to In Progress, Resolved and then Closed. Other workflows may have other status transitions.

Open
The issue is open and ready for the assignee to start work on it.
Backlog
Нужно запланировать задачу
Архив
Задачи с невысоким приоритетом, которые необходимо взять в работу
At work
This issue is being actively worked on at the moment by the assignee.
Done
Need review
Задача требует ревью
block
Задача заблокирована и работа над ней не может продолжаться
In test
Задача в процессе тестирования
Reopened
This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.
Ready to release
Задача прошла весь цикл, ожидает релиза на прод
Put to test
Задачу нужно протестировать
Need merge
stop

Resolutions

An issue can be resolved in many ways, only one of them being "Fixed". The defined resolutions are listed below. You can add more in the administration section.

Done
Work has been completed on this issue.
Won't Do
This issue won't be actioned.
Duplicate
The problem is a duplicate of an existing issue.
Cannot Reproduce
All attempts at reproducing this issue failed, or not enough information was available to reproduce the issue. Reading the code produces no clues as to why this behavior would occur. If more information appears later, please reopen the issue.
22 апр. 2025 09:46
22 апр. 2025 09:46
4 апр. 2025 06:44
4 апр. 2025 06:44
19 мар. 2025 17:03
19 мар. 2025 17:03
Declined
This issue was not approved.
Known Error
The problem has a documented root cause and a workaround.
Hardware failure
Software failure