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
Improvement
An improvement or enhancement to an existing feature or task.
Task
A task that needs to be done.
Sub-task
A component of a bigger parent Task.
New Feature
A new feature of the product, which has yet to be developed.
Bug
A problem which impairs or prevents the functions of the product.
Epic
Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.
For Sub-Task Issues
Sub-task
A component of a bigger parent Task.
Sub-bug
The sub-bug of the issue
Technical task
A technical task.
AI
Cyber Report Sub-Task
Sub-action-item
Anything that is not direct computing work (decision, information, purchase, ...)
DS Secondary Project
Create a Sub DS Project within the context of a Parent Main Project. It still follows the workflow, even when some steps are implicit and thus not need a explicit action.
Obs-Proj
Observational Project
Sub-feature
A Feature that is part of a bigger Capability (according to the Management Plan)
MRB
NCR Development

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.

Low
Minor loss of function, problem where easy workaround is present, or not urgent action item.
High
Fix/feature/action is needed urgently (crashes, potential loss of data, missing functionality)
Medium
Bug, missing functionality or action item that does not prevent normal operation, possibly with workarounds.
Blocker
Blocks development and/or testing work, production (online or offline) could not run.

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.

To Do
In Progress
This issue is being actively worked on at the moment by the assignee.
Reviewing
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.

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.
Item Received
Item has been received and logged in the inventory system.
Transfer
The issue is transferred to another area in JIRA for tracking and resolution.
Done
Work has been completed on this issue.
In progress
Unresolved
Won't Do
This issue won't be actioned.
Rejected
The issue has been rejected, i.e. there is no real problem or it will never be fixed.
Validated
The issue has passed Phase C validation.
Verified
The issue has passed Phase B verification.