Jira Concepts - Issues

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
Stories track functionality or features expressed as user goals.
Task
A task that needs to be done. (Migrated on 1 Oct 2024 22:08 UTC)
Bug
A problem which impairs or prevents the functions of the product. (Migrated on 1 Oct 2024 22:08 UTC)
New Feature
A new feature of the product, which has yet to be developed. (Migrated on 1 Oct 2024 22:08 UTC)
Improvement
An improvement or enhancement to an existing feature or task. (Migrated on 1 Oct 2024 22:08 UTC)
Epic
A big user story that needs to be broken down. Created by Jira Software - do not edit or delete.
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.

Highest
This problem will block progress.
High
Serious problem that could block progress.
Medium
Has the potential to affect progress.
Low
Minor problem or easily worked around.
Lowest
Trivial problem with little or no impact on progress.

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.
In Progress
This issue is being actively worked on at the moment by the assignee.
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
The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
Building
Source code has been committed, and JIRA is waiting for the code to be built before moving to the next status.
Build Broken
The source code committed for this issue has possibly broken the build.
To Do
In Progress
Done
Submitted
(Migrated on 1 Oct 2024 22:08 UTC)
Delivered
(Migrated on 1 Oct 2024 22:08 UTC)
To Do
(Migrated on 1 Oct 2024 22:19 UTC)
Done
(Migrated on 1 Oct 2024 22:19 UTC)
In Review
(Migrated on 1 Oct 2024 22:19 UTC)
New
A new pontential Security Risk has been discovered (Migrated on 1 Oct 2024 22:19 UTC)
Confirmed
A Security Risk has been confirmed (Migrated on 1 Oct 2024 22:19 UTC)
Fix In Progress
A Security Issue is being worked on (Migrated on 1 Oct 2024 22:19 UTC)
Fix accepted
Security Fix has been accepted, and will be merged (Migrated on 1 Oct 2024 22:19 UTC)
Implemented
(Migrated on 1 Oct 2024 22:24 UTC)
Received
First triage on this potential Security Issue (Migrated on 1 Oct 2024 22:31 UTC)
Under review
Security Fix is under review (Migrated on 1 Oct 2024 22:31 UTC)
Embargoed disclosure
This Security Issue has been Disclosed to a limited audience (Migrated on 1 Oct 2024 22:31 UTC)
Public disclosure
This Security Issue has been made public (Migrated on 1 Oct 2024 22:31 UTC)
Not a security bug
This is not a Security Issue (Migrated on 1 Oct 2024 22:31 UTC)
Hardening opportunity
This is not strictly a Security issue, but the issue can be hardened (Migrated on 1 Oct 2024 22:31 UTC)
Not a bug
This is not an Security Issue, nor a normal Issue. (Migrated on 1 Oct 2024 22:31 UTC)
Backlog
(Migrated on 1 Oct 2024 22:45 UTC)
Selected for Development
(Migrated on 1 Oct 2024 22:45 UTC)
To Do
In Progress
Ready for Launch
Launched
To Do
Drafting
In Review
Approved
Created
To Do
In Progress
Done

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.
Unresolved
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.
Not a Bug
Not Done
Work has not been completed on this issue.
Recommended