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
Problem
Track underlying causes of incidents. Created by JIRA Service Desk.
Change
Created by JIRA Service Desk.
Service Request with Approvals
For requests that require approval. Created by JIRA Service Desk
Service Request
Created by JIRA Service Desk.
Incident
For system outages or incidents. Created by JIRA Service Desk.
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.
Story
Created by Jira Software - do not edit or delete. Issue type for a user story.
New Feature
A new feature of the product, which has yet to be developed.
Task
A task that needs to be done.
Improvement
An improvement or enhancement to an existing feature or task.
P-Initiative
An initiative that applies to a specific project. A roll up level for Epics in a Plan or Program.
Choice
Open questions that need resolution
Template
Issue Type for Templates
Initiative
A roll up level for Epics in a Plan or Program.
Documentation
For Sub-Task Issues
Sub-task
The sub-task of the issue
Technical task
A technical task.
Sub-Template
Sub-Issue Type for Templates

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.
Major
Major loss of function.
Minor
Minor loss of function, or other problem where easy workaround is present.
Trivial
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
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.
Done
To Do
Accepted for Merge
Backlog
Ready for Bus. Owner Review
These issue's requirements has been fully analyzed and is ready for the Business Owner review and approval.
Ready for Requirements
This status is used for Requirements that are under development.
Not Assigned
These are issues that have been created and not assigned to a development path or BA path.
QA
Ready for Quality Assurance (in Staging)
Ongoing
This status is managed internally by JIRA Software
Under Review
Approved
Cancelled
Rejected
Ready for Development
An Issue transitions to this status when the Business Analysis has been completed and approved by the Business Owner.
Selected for Development
Active Backlog
Working BA Backlog for Kanban Board
Declined
This was auto-generated by JIRA Service Desk during workflow import
Waiting for support
This was auto-generated by JIRA Service Desk during workflow import
Waiting for customer
This was auto-generated by JIRA Service Desk during workflow import
Pending
This was auto-generated by JIRA Service Desk during workflow import
Canceled
This was auto-generated by JIRA Service Desk during workflow import
Escalated
This was auto-generated by JIRA Service Desk during workflow import
Waiting for approval
This was auto-generated by JIRA Service Desk during workflow import
Awaiting CAB approval
This was auto-generated by JIRA Service Desk during workflow import
Planning
This was auto-generated by JIRA Service Desk during workflow import
Awaiting implementation
This was auto-generated by JIRA Service Desk during workflow import
Implementing
This was auto-generated by JIRA Service Desk during workflow import
Peer review / change manager approval
This was auto-generated by JIRA Service Desk during workflow import
Work in progress
This was auto-generated by JIRA Service Desk during workflow import
Completed
This was auto-generated by JIRA Service Desk during workflow import
Under investigation
This was auto-generated by JIRA Service Desk during workflow import
Current Sprint
This status is managed internally by JIRA Software
Staging Q/A
This status is managed internally by JIRA Software
Draft
Published
Archived
Q/A
This status is managed internally by JIRA Software
DevComplete
This status is managed internally by JIRA Software
In Dev
This status is managed internally by JIRA Software
In Review
Discovery/Testing
This status is managed internally by Jira Software
Ready for Release

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.
Invalid
The problem is not actually a bug, possibly resulting from user error, bad documentation, etc.
Completed
Work completed on a task/improvement
Done
Won't Do
This issue won't be actioned.
Declined
This issue was not approved.