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
Incident
Security Issue
This issue has security implications.
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.
Bug
A problem which impairs or prevents the functions of the product.
New Feature
A new feature of the product, which has yet to be developed.
Task
A task that needs to be done.
Improvement
An improvement or enhancement to an existing feature or task.
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.

Blocker
Blocks development and/or testing work, production could not run.
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.

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.
Unverified Fix
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.
Invalid
The issue is invalid, it is a support request, a stub or has no information.
Awaiting Information
Further information from the reporter is required to commence work.
Patch Awaiting Review
A patch solving the issue has been proposed, but is awaiting review by a development team members.
Unmerged Fix
The fix is ready for merging into the main repository
Patch Needs Work
A patch has been reviewed but needs further work before it can be merged.
Awaiting Team Input
Input from other team members is required.
Reviewed
This issue has been reviewed and a solution provided. The ticket will remain open for a short period of time before closing.
Support Request
This issue should be directed to the support forums and is not appropriate for this tracker.
Done
To Do
Review Later
This issue will be reviewed at a later date.
Blocked
In Progress by OSUOSL
In Progress By Us
Confirmed
A bug which has been confirmed
Have regression test
A regression test has been implemented, committed and disabled

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.
Invalid
The reported issue is invalid.
Done
Resolved
Resolved
Closed
Closed
Won't Do
This issue won't be actioned.