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.

Improvement
An improvement or enhancement to an existing feature or task.
Bug
An unwanted behavior within the product that causes harm to existing functionality.
New Feature
A new feature of the product, which has yet to be developed.
Task
A task that needs to be done.
Story
A user story.
Epic
A big user story that needs to be broken down.

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.

Critical
Issue breaks core functionality.
Highest
Issue breaks important functionality.
High
Issue breaks common functionality.
Medium
Issue has the potential to break common functionality.
Low
Issue breaks minor functionality or is easily worked around.
Lowest
Issue is trivial with little or no impact on minor functionality.
None
Issue has not yet received priority classification.
Feature Request
Issue is a feature request or suggestion and has no impact on any functionality.

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 has been reported and is waiting processing by an administrator. This is an editable status.
In Progress
The issue is being actively worked on at the moment by the assignee.
In Review
The issue is being tested and reviewed by the assignee or other party.
Reopened
The issue was once resolved but the resolution was deemed incorrect.
Ready for Default
The issue is considered to be finished and is ready to be deployed to the default branch.
Deployed To Default
The issue has been deployed into the default branch.
Blocked
The issue cannot be worked on as a different issue is blocking it.
User Error
The issue is deemed as not a bug but could still be considered problematic. For example, user errors end up in this resolution.
Cannot Reproduce
The issue cannot be reproduced. It is either solved by an earlier deployed fix, lacks sufficient information to be reproduced or cannot simply be reproduced.
Duplicate
The issue is a duplicate of another issue. This resolution exist to remove duplicates from the backlog.
Ready for Experimental
The issue's internal testing has been completed and is ready to be deployed into the experimental branch.
Deployed To Experimental
The issue is currently deployed and being tested in the experimental branch.
Investigate
The issue has been approved for investigation initiation and is awaiting an assignee. This is an editable status.
Won't Do
An issue suggestion such as an improvement or new feature will for some reason not be considered.
Awaiting Development
The issue has been checked, cleaned and approved for development and is awaiting initiation.
Abandoned
The issue is for some reason (most likely administrative or privacy) put here and abandoned. Issues cannot be seen but edited.
Suggested
The issue has been suggested and is awaiting consideration.
Fix Deployed
The issue has already had a fix deployed in either experimental or default branch.
Building
Source code has been committed, and JIRA is waiting for the code to be built before moving to the next status.
No Bug
An issue is not considered as a bug. Functionality is expected.
Backlog
Build Broken
The source code committed for this issue has possibly broken the build.
Selected for Development
Done

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.

Done
The issue work has been completed.
Won't Do
The issue won't be actioned upon.
Duplicate
The issue is a duplicate of an existing issue.
Cannot Reproduce
All attempts at reproducing this issue failed, or not enough information was available to reproduce the issue.
No Bug
The issue's occurred behaviour is as intended or will require a separate issue to be mitigated (if usage error).
Abandoned
The issue has been abandoned.