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
-
Task
- Other team work items not included in the above issue types. This work should be pointed.
-
Sub-task
- The sub-task of the issue
For Sub-Task Issues
-
Development Subtask
- Generic subtask for developer work.
-
Tester Subtask
- Generic Subtask for tester work
-
Release Sub-Task
-
Code Review
-
Sub-task
- The sub-task of the issue
-
OB subtask
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.
-
TBD
-
High
- Serious problem that could block progress.
-
2-Normal
- Created by JIM during import process
-
Low
- Minor problem or easily worked around.
-
Lowest
- Trivial problem with little or no impact on progress.
-
Medium
- Has the potential to affect progress.
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.
- Cancelled
- New Request
- Active Maintenance
- Due For Renewal
- Quotes in Process
- Purchase in Process
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.