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
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
- A problem which impairs or prevents the functions of the product.
- A task that needs to be done.
- Created by Jira Software - do not edit or delete. Issue type for a user story.
- Change Request
- Issue for requesting a change.The behavior of the function or API before and after the change differ
- Issue requesting a code refactoring. The behavior of the code to refactor does not change. Regression test must all pass after refactor without making any changes to the tests itself.
- Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.
For Sub-Task Issues
- The sub-task of the issue
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.
- This problem will block progress.
- Serious problem that could block progress.
- Has the potential to affect progress.
- Minor problem or easily worked around.
- Trivial problem with little or no impact on progress.
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.
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
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.
- 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.
- This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.
- A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.
- The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
- Selected for Development
- Issues selected to be discussed in a refinement meeting. * A group of project participants will discuss the issue maken ing sure it is understodd and ready for development * The discussion will include an estimation using story points
- Issues has passed DOR criterian and is ready and waiting for development.
- Issue development is finished. * Merge request has been posted and built by CI
- In Review
- Issue is reviewd according to DOD
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.
- Work has been completed on this issue.
- Won't Do
- This issue won't be actioned.
- 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.