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
Access
For new system accounts or passwords. Created by JIRA Service Desk.
Bug
A problem which impairs or prevents the functions of the product.
Change
For system upgrades or alterations. Created by JIRA Service Desk.
Data Flow
Assistance locating images flowing from another source with Wash U. (CCIR, Bay 3, PACS, etc.)
Epic
Created by JIRA Agile - do not edit or delete. Issue type for a big user story that needs to be broken down.
Exception
Fault
Track system outages or incidents. Created by JIRA Service Desk.
Feature
Feature
Improvement
An improvement or enhancement to an existing feature or task.
Initiative
A collection of epics.
Inquiry
Inquiry
IT Help
For general IT problems and questions. Created by JIRA Service Desk.
New Feature
A new feature of the product, which has yet to be developed.
New Ticket
Default issue type for new tickets.
Schedule Item
Schedule Item
Site Usage
Question about or assistance with standard site usage.
Story
Created by JIRA Agile - do not edit or delete. Issue type for a user story.
System Issue or Outage
Customer is reporting a suspected funtional issue with the site.
Task
A task that needs to be done.
Test
This Issue Type is used to create Zephyr Test within Jira.
For Sub-Task Issues
Sub-task
The sub-task of the issue
Technical task
A technical task.
Test Sub-task

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.

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.

To Do

Represents anything new

In Progress

Represents anything in the process of being worked on

No Category

A category is yet to be set for this status

Done

Represents anything for which work has been completed

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
Closed
The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
Test Writing in Progress
Use this status when the creation/writing of the test is in progress and is NOT ready for execution
Deprecated
Use this status when a test is no longer valid or has been replaced.
To Do
Done
Define Functional Spec
Initial part of the User Story workflow.
Awaiting Customer Approval
Used multiple times in User Story workflow
Develop Code
Required part of User Story workflow
Perform Functional Tests
Required part of User Story workflow
Develop Wireframe and Functional Tests
Required part of User Story workflow
Integrate with XNAT (core/module)
In Test
This status is managed internally by JIRA Agile
In Review
Awaiting Regression Test
Resolved, tested if possible, awaiting regression tests before ticket can be closed.
Ready for Test Execution
Active
The Test is written, reviewed and ready to be executed
Ready for Review
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
Planning
This status is managed internally by JIRA Agile
Code Complete
This status is managed internally by JIRA Agile

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.
Won't Implement
Won't Implement
By Design
By Design
Already Exists
Already Exists
Responded
Responded
SPAM
SPAM
Won't Respond
Won't Respond
Completed
Completed
Done
GreenHopper Managed Resolution
Won't Do
This issue won't be actioned.
Not A Bug
Behavior is expected or due to other causes