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
Service Request with Approvals
For requests that require approval. Created by JIRA Service Desk
Epic
Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.
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.
New Feature
A new feature of the product, which has yet to be developed.
Task
A task that needs to be done.
Enhancement
An improvement or enhancement to an existing feature or task.
Access
For new system accounts or passwords. Created by JIRA Service Desk.
FAI Request
First Article Inspection Request
SAR
Employee Status Change
Termination
Incident
For system outages or incidents. Created by JIRA Service Desk.
Service Request
Created by JIRA Service Desk.
Change
Created by JIRA Service Desk.
Problem
Track underlying causes of incidents. Created by JIRA Service Desk.
Maintenance
Large Project
Projects larger than $100K
Small Project
Project $100K or less
Deployment
Roadmap
SPR
Certification Request
Innovation
Internal
MOL
NPI A
NPI B
Periodic Software Release
Create Microsoft Teams Team
An issue to create a MS Teams team.
DoC/Records Request
Rework
Software Change
Software Change Request
Environmental Change
Environmental Change Request
Technical Question
Programming or technical questions
Certification
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.
For Sub-Task Issues
Sub-task
The sub-task of the issue

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.

Committed
Committed to Customer
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.
Emergency
High
Serious problem that could block progress.
Medium
Has the protential to affect progress.
Low
Minor problems or easily worked around.
Standard Project
Key Project
Not Yet Determined

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
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.
Approved
The issue has been reviewed and approved.
Paperwork
This status is managed internally by JIRA Software
Report
This status is managed internally by JIRA Software
Testing
This status is managed internally by JIRA Software
Cancelled
This status is managed internally by JIRA Software
Planning
Planning Status
Needs Triage
New
Development
Awaiting Approvals
Implementation Pending
Implementation In Progress
Done
Escalate
Requested
Scheduled
Backlog
Issue is parked on the backlog.
In Review
To Do
Waiting
Waiting or blocked.
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
New Request
More Info Needed
ME Acceptance
Mfg Acceptance
Needs Deviation
Mfg OQC
TechSupp OQC
Waiting For Feedback
Customer Rejected
Customer Accepted
Mfg Planning
Work Order Release
Sales Order Entry
PM Acceptance
Ready To Ship
On Hold
Awaiting approval
This was auto-generated by JIRA Service Desk during workflow import
Rejected
This was auto-generated by JIRA Service Desk during workflow import
Awaiting implementation
This was auto-generated by JIRA Service Desk during workflow import
Selected for Development
Ready for Deploy
Triage
Waiting - 2
Hold
New Feature
Task
Improvement
Consideration
Execution
Complete
This status is managed internally by JIRA Software
Under Review
Declined
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
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
Director Approval
Approval Check
Check if all members of the CAB have approved of the change
Change Control Manager
Opem
Concept
Research
Diligence
Launch
Drafting
Add Graphics
Tech Review
Copyedit
Moved to Kentico
Fix Resolution

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.
Rejected
This issue was not approved.
Declined
This issue was not approved.