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
Test
This Issue Type is used to create Zephyr Test within Jira.
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.
Research
Template
Issue Type for Templates
Support
Investigation in support of a product or tool
Access
For new system accounts or passwords. Created by JIRA Service Desk.
Testing request
The testing request
Position
Candidate
Candidate for open EBT position
Product Feature
Kublr product issue type
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.
Recruit
Candidate for position
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.
Cosmetic
Cosmetic problem like misspelt words or misaligned text.
High Priority
Low Priority
1 - Critical
Dispatch (DoB) Project
2 - High
Dispatch (DoB) Project
3 - Medium
Dispatch (DoB) Project
4 - Low
Dispatch (DoB) Project
5 - Trivial
Dispatch (DoB) Project

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.
New
In Review
Team lead reviews the documentation
Done
Internal Review
Ready to Test
In Testing
Verified
Feedback
This status is managed internally by JIRA Software
Review
This status is managed internally by JIRA Software
Ready in DEV
This status is managed internally by JIRA Software
In QA
This status is managed internally by JIRA Software
Not Ready
This status is managed internally by JIRA Software
Fixed
Developer fixed a bug
Can't Reproduce
Reported issue is not reproducable
Implemented
This status is managed internally by JIRA Software
Deployed
This status is managed internally by JIRA Software
Invalid\Obsolete
This status is managed internally by JIRA Software
To Do
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
Unable to duplicate
This status is managed internally by JIRA Software
Backlog
Selected for Development
Analysis
Preparing requirements, business needs, acceptance criteria, UX
READY TO DEV
Ready to Review
Commits are squashed, clear commit message has created.
REVIEWED
Team lead/responsible member has pre-tested, reviewed changes.
Delivered
Deployed to Production
Rejected
Debug
Abandoned
This status is managed internally by JIRA Software
Ready For Deploy
Deployed to DEV
This status is managed internally by JIRA Software
Deployed to QA
This status is managed internally by JIRA Software
Need SME
Failed acceptance
This status is managed internally by JIRA Software
Blocked
This status is managed internally by JIRA Software
Validated
This status is managed internally by JIRA Software
Cannot duplicate
This status is managed internally by JIRA Software
Testing
This status is managed internally by JIRA Software
Need more info
Blocked by Kroger team. Needs some more information about the subject.
Returned
This status is managed internally by JIRA Software
Acceptance
This status is managed internally by JIRA Software
Invalid/Blocked
This status is managed internally by JIRA Software
Experiment failure
This status is managed internally by JIRA Software
Duplicate
This status is managed internally by JIRA Software
Feedback Required
Accepted by customer
Reviewed & Deployed
Ready in DEV - 2
Needs Definition
This status is managed internally by Jira Software
QA
This status is managed internally by Jira Software
Needs DoD
This status is managed internally by Jira Software
Screening
PEER INTERVIEW
DOCS INTERVIEW
SLT INTERVIEW
OFFER NEGOTIATION
OFFER ACCEPTED
OFFER REJECTED
CLIENT INTERVIEW
TEAM PLACEMENT
Under Review
Approved
Cancelled
Draft
Published
Archived
Design
Requirements being designed for UI screens and flow
Ready for Development
Won't Do
Client 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.

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
Won't Do
This issue won't be actioned.
Verified
Issue is tested and verified