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
Story
A user story. Created by JIRA Software - do not edit or delete.
User interface design
Visual design of the user interface
Technical design
Designing architecture and thinking about how stuff should be done
Research
Research in order to understand a problem area better and to discover what options exist for solving it
Idea
Bug
A problem which impairs or prevents the functions of the product.
Task
A task that needs to be done.
Epic
A big user story that needs to be broken down. Created by JIRA Software - do not edit or delete.
For Sub-Task Issues
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.

Highest
This problem will block progress.
High
Serious problem that could block progress.
Medium
Has the potential to affect progress.
Low
Minor problem or easily worked around.
Lowest
Trivial problem with little or no impact on progress.

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.
Building
Source code has been committed, and JIRA is waiting for the code to be built before moving to the next status.
Build Broken
The source code committed for this issue has possibly broken the build.
Selected for development
Done
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
UX + Code review
This status is managed internally by JIRA Software
Needs Code Review
This status is managed internally by JIRA Software
Waiting Upstream
This status is managed internally by JIRA Software
Deployed to Dev
This status is managed internally by JIRA Software
test
In Design
Ready for development
Needs deploy
UX review
Backlog
Design Review
Needs UX review
Deployed to production
Needs Review
To Do
Review
This status is managed internally by Jira Software
Verified
This status is managed internally by Jira Software
Awaits Info
This status is managed internally by Jira Software
Blocked
Issue is blocked, because it's pending external actions
To Do
In Progress
In review
Deployed to PROD
Ready for PROD
Deployed to DEV
READY FOR DEV

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
Work has been completed on this issue.
Won't Do
This issue won't be actioned.
Duplicate
The problem 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. Reading the code produces no clues as to why this behavior would occur. If more information appears later, please reopen the issue.