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.
Backport
To identify issues that need to be backported to previous releases.
Engineering Test
For adding, improving or fixing bugs in eng test suites
Epic
Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.
Sub-task
The sub-task of the issue
Bug
A problem which impairs or prevents the functions of the product.
Story
Created by Jira Software - do not edit or delete. Issue type for a user story.
Question
Build Failure
Task
A task that needs to be done.
Spec Change
New Feature
A new feature of the product, which has yet to be developed.
Static Code Analysis Finding
Vulnerability
Technical Debt
Tasl
Documentation
Investigation
Release
Server Releases
FLW Epic
Parent Epic
Workload
For Sub-Task Issues
Refactor Sub-Task
Approval Sub-Task
Certification(s) Mapping
Which certifications does this Unit belong to?
LGTM
LGTM for Research efforts
Sub-bug
A problem which impairs or prevents the functions intended in the parent issue
Sub-CR
A change request to the parent issue
Title and Abstract (Sub-type)
Kernel Release Sub-Task
Driver Release Sub-Task
MMS Release Sub-Task
Sub-task
The sub-task of the issue
Backport Sub-Task
CRM Sub-Task
CRM Sub-Task
Curriculum Sub-Task
Sub-task used by the PS Curriculum team to keep track of their development efforts

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 - P1
Blocks development and/or testing work, production could not run.
Unknown
Priority not determined yet.
Trivial - P5
Cosmetic problem like misspelt words or misaligned text.
Critical - P2
Crashes, loss of data, severe memory leak.
Minor - P4
Minor loss of function, or other problem where easy workaround is present.
Major - P3
Major loss of function.

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.

In Progress
This issue is being actively worked on at the moment by the assignee.
Needs Triage
Rejected
Ready for Work
Exception in Review
Remediation in Review
Needs Backport
Temporary Exception
Remediation Complete
Remediation Pending Release
Waiting (Blocked)
In Code Review
Closed
The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
Scheduled
Accepted
Waiting To Reoccur
On Deck
Pulled from the backlog and ready for work
Needs Scheduling
Needs Discussion
Open
Waiting For User Input
Needs Merge
Needs Verification
Investigating
Blocked
Status for tickets that need to be escalated and unblocked on our team.
Backlog
Execution Blocked
Dependency exists that blocks execution. The dependency may be engineering effort related, or it may be due to alternative factors (e.g. an external vendor, or internal procurement). This does not require linkage to another separate ticket.
Defining
Development Complete
Execution is complete. Remains in this status if Fix Version is empty.
Released
This issue is part of a published release and should not be reopened.
Canceled
This was auto-generated by Jira Service Desk during workflow import
Documentation
Live
The Cloud Services - Atlas Growth epic is live on production. Epic is still considered in progress awaiting for the analysis phase.
In Analysis
Needs Decision
Atlas Growth experiment where analysis is complete, but pending a decision on experiment outcome.
Launch
(Experiment-only) Status to represent that a variant is ready to expose to all users, excluding Holdouts.
Wrap-up
For any required engineering work after an A/B experiment has been completed.
Waiting for Reporter
Needs Review
Implementing
In Review
Debugging With Submitter
This status is managed internally by JIRA Software

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. This can happen when a user never responds with a request for additional information
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.
Works as Designed
Either expected feature or user error.
Gone away
Person who logged the issue is no longer responding. In SERVER, used for bugs that are no longer present in a newer version of the product
Community Answered
The users provided the solution for this issue
Done
Work has been completed on this issue.
Won't Do
This issue won't be actioned.
Declined
This issue was not approved.