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
Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.
Created by Jira Software - do not edit or delete. Issue type for a user story.
Product Requirement
Requirement that describes a business use case that needs to be solved via a new feature or software.
Technical Requirement
Requirement that describes a technical approach to satisfy a business requirement. This will need to be implemented via one or more coding stories.
Test Case
A test case to be discussed, described, and implemented
A set of tasks that need to be completed to satisfy a requirement
A collection of epics
Business Requirement
Requirement that captures business needs in the format of a User-Story. It describes what functionality is expected, by whom and why it is relevant. It should be broken-down into Technical Requirements before implementation.
A task that needs to be done.
A problem which impairs or prevents the functions of the product.
An improvement or enhancement to an existing feature or task.
New Feature
A new feature of the product, which has yet to be developed.
For Sub-Task Issues
The sub-task of the issue
Detailed requirement

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.

Task to be completed ASAP, unless something more critical comes along
Blocks progress on the main deliverables
Needs to be fixed urgently, or is otherwise in the critical path of the project
Middle ground priority -- neither high, not low.
Good task to do when there is nothing else to work on
This issue should not be worked on at the moment, because it's still unclear whether any work is needed at all.


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.


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.

This requirement is in Draft and still needs some discussion and possible amendment
In Progress
This issue is being actively worked on at the moment by the assignee.
This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.
A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.
The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
To do
Under review
On hold
Selected for Development
Selected for Dev
Development team has picked up this technical requirement for implementation
Selected for Technical Review
Technical team has selected this product requirement for review and conversion into technical requirements
In Test
Module is being tested
In Review
Item discarded
Still being written
This requirement was added for the [email protected] imported prplWrt workflow
Merged In Master
This requirement was added for the [email protected] imported prplWrt workflow
This requirement was added for the [email protected] imported prplWrt workflow
Action Required
This requirement was added for the [email protected] imported prplWrt workflow
Not Compliant
Partially Compliant
Not Applicable
Ready for Review
Waiting for feedback
We need some more information from the community/reporter/...


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.

Work has been completed on this issue.
Won't Do
This issue won't be actioned.
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.