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
Access
For new system accounts or passwords. Created by JIRA Service Desk.
Application issue
Bug
A problem which impairs or prevents the functions of the product.
CR
Change
For system upgrades or alterations. Created by JIRA Service Desk.
Connector
Database issue
Documentation
Epic
Created by JIRA Agile - do not edit or delete. Issue type for a big user story that needs to be broken down.
Fault
Track system outages or incidents. Created by JIRA Service Desk.
Feature
Feature
HW system issues
IT Help
For general IT problems and questions. Created by JIRA Service Desk.
Improvement
An improvement or enhancement to an existing feature or task.
Integration
New Feature
A new feature of the product, which has yet to be developed.
Purchase
Track items that need to be bought. Created by JIRA Service Desk.
Question
Regression
Story
Created by JIRA Agile - do not edit or delete. Issue type for a user story.
Support Ticket
Support Ticket
Task
A task that needs to be done.
For Sub-Task Issues
Sub-task
The sub-task of the issue
Technical task
Created by JIRA Agile - do not edit or delete. Issue type for a technical 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.

Deferred
Placeholders request for future
Urgent
To be fixed as soon as possible
Normal
To be fixed once possible

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.

Opened
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
Need More Info
More infor from Requester
Cancelled
Dev Scheduled
QA In Progress
Implementation in progress
Dev Paused
Ready for QA
Rejected
Wont Fix
Pending
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
Waiting for Triage
This was auto-generated by JIRA Service Desk during workflow import
Open Bug
Pending Customer
Pending Info from Customer
Pending Design Session
L1 In Progress
L2 In Progress
L3 In Progress
Waiting Final Solution
Bug/s Found
Pending Requirements
Convert to Epic
Registered
Registered Ticket by L1 or Help Desk
Customer Contacted
1st Response when Help Desk/ L1 assigned contact the customer
To Be Released
T_Pend Req
T_Pend Des
T_Dev In Prog
T_RFQA
T_Closed
OPEN-ISSUE
Ready for PROD
Backlog
Selected for Development
Released on PROD
This status is managed internally by JIRA Agile
Request to re-open
Client requested to re-open
In Review

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.

Not Fixed
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.
Done
Work has been completed on this issue.
Cancelled