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
Project Goal
A major goal in a project timeline to help organize project tasks
CD
LP
Tape
IU Performance
Feedback
Testing feedback that will turn into another issue based on scope
Use Case
Use Case: used for requirements manangement for development projects in JIRA
Design
Design activity: used for tracking tasks for design activities, like wireframing, system designs, etc.
Notes
For Variations on Video
Project
Case - Repository
For use with Case Management Solution
Case - OJS/OCS
For use with Case Management Solution
Case - RDM
For use with Case Management Solution
Case - DCS
For use with Case Management Solution
Case - IDAH
For use with Case Management Solution
Case - DCS/IDAH
For use with Case Management Solution
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.
New Feature
A new feature of the product, which has yet to be developed.
Story
Created by Jira Software - do not edit or delete. Issue type for a user story.
Task
A task that needs to be done.
Improvement
An improvement or enhancement to an existing feature or task.
For Sub-Task Issues
Design (sub-task)
Design activity: used for tracking tasks for design activities, like wireframing, system designs, etc.
Use Case (sub-task)
Design activity: used for tracking tasks for design activities, like wireframing, system designs, etc.
Consultation
For use with Case Management Solution
Sub-task
The sub-task of the issue
Technical task
A technical task.
NotesVOV
For Variations on Video

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.
Trivial
Cosmetic problem like misspelt words or misaligned text.
Project launch
Project launch activities
Core development
Core development
Features: Priority 1
Features: Priority 1
Features: Priority 2
Features: Priority 2
Features: Priority 3
Features: Priority 3
Version Release
Version release activities
Sub-task: Priority 1
Sub-task: Priority 1
Sub-task: Priority 2
Sub-task: Priority 2
Sub-task: Priority 3
Sub-task: Priority 3

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.
Published
Awaiting Redelivery
Audio Redelivered
Blocked
Use when an issue has a external blocker preventing resoloution
Proposed
In Planning
Disapproved
Cancelled
Approved
Access Interruptions
This status is managed internally by JIRA Software
Resource Procurement
This status is managed internally by JIRA Software
Trials
This status is managed internally by JIRA Software
Done Test
This status is managed internally by JIRA Software
Contact Vendor
This status is managed internally by JIRA Software
Proxy
This status is managed internally by JIRA Software
Access & Notifications
This status is managed internally by JIRA Software
Trial Posted
This status is managed internally by JIRA Software
Done
This status is managed internally by JIRA Software
License Infringements
This status is managed internally by JIRA Software
Bibloads
This status is managed internally by JIRA Software
Cataloging Notified
This status is managed internally by JIRA Software
In QC
Issue is being QC'd
ERA-Activ-03
This status is managed internally by JIRA Software
ERA-Bibloads
This status is managed internally by JIRA Software
ERA-Bibloads-01
This status is managed internally by JIRA Software
ERA-Help-01
This status is managed internally by JIRA Software
ERA-Procure-01
This status is managed internally by JIRA Software
ERA-Procure-03
This status is managed internally by JIRA Software
ERA-Procure-04
This status is managed internally by JIRA Software
LIBSER-Price-03
This status is managed internally by JIRA Software
LIBSER-TT-05
This status is managed internally by JIRA Software
ERA-Activations
This status is managed internally by JIRA Software
ERA-Activ-01
This status is managed internally by JIRA Software
ERA-Activ-02
This status is managed internally by JIRA Software
ERA-Activ-04
This status is managed internally by JIRA Software
ERA-Bibloads-02
This status is managed internally by JIRA Software
ERA-Helpdesk
This status is managed internally by JIRA Software
ERA-Help-02
This status is managed internally by JIRA Software
ERA-ResourceManagement
This status is managed internally by JIRA Software
ERA-RM-01
This status is managed internally by JIRA Software
ERA-RM-02
This status is managed internally by JIRA Software
ERA-RM-03
This status is managed internally by JIRA Software
ERA-LicenseInfringements
This status is managed internally by JIRA Software
ERA-LicenseInfringe-01
This status is managed internally by JIRA Software
ERA-LicenseInfringe-02
This status is managed internally by JIRA Software
ERA-LicenseInfringe-03
This status is managed internally by JIRA Software
ERA-Procurement
This status is managed internally by JIRA Software
ERA-Procure-02
This status is managed internally by JIRA Software
ERA-Procure-05
This status is managed internally by JIRA Software
ERA-Procure-06
This status is managed internally by JIRA Software
LIBSER-Activ-04
This status is managed internally by JIRA Software
LIBSER-Procure-05
This status is managed internally by JIRA Software
LIBSER-Head
This status is managed internally by JIRA Software
LIBSER-Head-01
This status is managed internally by JIRA Software
LIBSER-Head-02
This status is managed internally by JIRA Software
Serials Acquisitions Head
This status is managed internally by JIRA Software
To Do
ERA-ACTIV-05
This status is managed internally by JIRA Software
ERA-ACTIV-04a
This status is managed internally by JIRA Software
LIBSER-Problem-03
This status is managed internally by JIRA Software
ERA-BIBLOADS-01A
This status is managed internally by JIRA Software
Backlog
Selected for Development
Reported
This status is managed internally by JIRA Software
Assigned
This status is managed internally by JIRA Software
On Hold
Awaiting Patron Response
ERA-Bibloads-00
This status is managed internally by JIRA Software
In Review
ERA-Cancellations
This status is managed internally by JIRA Software
ERA-Cancel-01
This status is managed internally by JIRA Software
ERA-Cancel-02
This status is managed internally by JIRA Software
ERA-Cancel-03
This status is managed internally by JIRA Software
ERA-Cancel-04
This status is managed internally by JIRA Software
ERM-RM-00
This status is managed internally by JIRA Software
Committed
This status is managed internally by JIRA Software
Merged
This status is managed internally by JIRA Software
Ready
This status is managed internally by Jira Software
QA
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.
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.
Completed
Feature has been completed but not necessarily put into use
Deployed
Feature has been completed and deployed
Completed (Vov Scrum)
Abandonded (Vov Scrum)
Resolved
Issue resolved but requires additional workflow step to be closed
Done
GreenHopper Managed Resolution
Won't Do
This issue won't be actioned.