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
IT Help
For general IT problems and questions. Created by JIRA Service Desk.
Purchase
Track items that need to be bought. Created by JIRA Service Desk.
Fault
Track system outages or incidents. Created by JIRA Service Desk.
Access
For new system accounts or passwords. Created by JIRA Service Desk.
Suggestion
Campus Services Suggestion Box Issue Type
Emergency Change
HHMI Change Management Emergency Change
Normal Change
HHMI Change Management Normal Change
Standard Change
HHMI Change Management Standard Change
Engineering PM Service
Engineering Scheduled Tasks
Production Support
Protected Field Changed
Immediate
Camera Freeze
Bowl camera freezes
Boarding
Content Change
Candidate
User Orders
Section Issue
Production Support - Science Team
Custom Production Support Issue Type for Science Capability Team.
Spike
Spike - COLLAB
New Account Request
Request access to JIRA
New Project Request
Other
Host Migration Task
Task specifically related to a host migration
Data Migration (Auditable)
Production data migration. Needs to follow audit process.
Bug (Auditable)
Not working as expect. Changes need to follow audit process.
New Feature or Enhancement (Auditable)
A new feature or modification to existing functionality. Changes need to follow audit process.
User Request
Test
For creating tests in JIRA
Data Migration
Production data migration. No audit process
QC Failure
A quality control issue
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 or Enhancement
A new feature or modification to existing functionality
Task
A task that needs to be done.
Improvement
An improvement or enhancement to an existing feature or task.
New Feature
A new feature of the product, which has yet to be developed.
Support
For customer support issues. Created by JIRA Service Desk.
Incident
For system outages or incidents. Created by JIRA Service Desk.
Service Request
Created by JIRA Service Desk.
Service Request with Approvals
For requests that require approval. Created by JIRA Service Desk
Change
Created by JIRA Service Desk.
Problem
Track underlying causes of incidents. Created by JIRA Service Desk.
For Sub-Task Issues
Technical Task (Auditable)
Sub-task requiring development. Must follow audit process
Test (sub-task)
Sub-task
The sub-task of the issue
Technical task
A technical task.
AP Approval
Banking Approval
FP&A Approval
P2P Approval

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.
Normal
Normal task priority, no loss of function, operational changes.
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.

Deferred
Open
The issue is open and ready for the assignee to start work on it.
Reopened
This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.
To Do
Gathering Requirements
Research and gather requirements
Feedback
Assigned
In Review
In Progress
This issue is being actively worked on at the moment by the assignee.
In Development
Waiting for Code Review
Code Review
Remigrate to Testing
Pending User Approval to Test
User Approval to Test
IT Manager Approval to Test
Waiting for QA
QA Review
User Approval to Production
In UAT / Pending User Approval to Production
User Testing or Waiting for User's Approval to Production
IT Manager Approval To Production
Acknowledged
Migrated to Test
Migrated to Production
Confirmed
Documentation
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
Waiting for Approval to Test
Waiting for Approval to Production
Reviewing
Business Approval
Release Mgmt Approval
Ready for Production
All QA/UAT is complete, and issue is ready to move to production. Close when deployed.
Backlog
Selected for Development
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
Awaiting approval
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
Under review
This was auto-generated by JIRA Service Desk during workflow import
Waiting for vendor
Product Owner Approval
This status is managed internally by JIRA Software
On Hold
Project is on hold
2nd Approval
Cancelled
Change In Process
Production Ready
Resubmittal Required
Awaiting Resolution
HQ Project Task
ShipTo Location Task 1
Asset Loc/Work Space Task
Expense Item Task
Cost Center Task
Other WorkTag Tasks
MCC Task
CC Roles Task
ShipTo Location Task 2
Primary Approved
On Order
Researching
Project
Transferred
FP & A Approvals
Inactive Cost Center
Approval Denied
Primary Approval
Inactivate Cost Center task
Inactivate SC Task
Ready For Release
CCB Approval

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.
Deferred
Issue will not be worked on now, but may be needed in distant future.
Declined
This issue was not approved.
Known Error
The problem has a documented root cause and a workaround.
Hardware failure
Software failure
Unresolved