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.
Project task
Application Crash
Epic
Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.
Idea
Created by Jira Software - do not edit or delete. Issue type for a user story.
Task
Improvement
Error
Server
Workflow
Question
Release
Vacation
Item
Consultation
Demo Request
Change Request
Hypothesis
Initiative
Technical Question
Bug
New feature
Problem
Instance
Sale
Human
For Sub-Task Issues
Sub-Task

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.

Blocker
Blocks development and/or testing work, production could not run.
Critical
Crashes, loss of data, severe memory leak.
High
Medium
Minor
Minor loss of function, or other problem where easy workaround is present.
Cosmetic
Cosmetic problem like misspelt words or misaligned text.

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
In Progress
Reopened
This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.
Resolved
A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.
Closed
Potential
Установка контакта с потенциальным клиентом, выяснение проблемных мест.
Expertise
Проведение оценки, создание КП, презентации, демо
Contracting
Формализация сделки, оформление договора, предоплата
Delivering
Сопровождение этапов поставки по графику платежей, подготовка счетов и актов
Archived
Archived
Waiting for Customer
We are waiting for you...
Investigation
We are thinking about you...
Остановлен
Удалено
Работает
Maintenance
В статусе Maintenance ведутся работы. Например, обновление.
Waiting for Closing
We are waiting for you...
Frozen
Testing
Review
Development
Documenting
Merging
Onboarding
Landing
Takeoff
Releasing
Analysis
Backlog
Released
To Do
Retrospective
New
Post-release
moved to cloud
Done
New hypothesis
Collection
Rejected
New Initiative

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.

Fixed
A fix for this issue is checked into the tree and tested.
Won't Fix
The problem described is an issue which will never be fixed.
Duplicate
The problem is a duplicate of an existing issue.
Incomplete
The problem is not completely described.
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.
Frozen
Done
Work has been completed on this issue.
Won't Do
This issue won't be actioned.