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
- Created by JIRA Software - do not edit or delete. Issue type for a big user story that needs to be broken down.
- Created by JIRA Software - do not edit or delete. Issue type for a user story.
- A task that needs to be done.
- A problem which impairs or prevents the functions of the product.
- An improvement or enhancement to an existing feature or task.
- New Feature
- A new feature of the product, which has yet to be developed.
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.
- A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.
- To Do
- In Review
- Selected for Development
- A new pontential Security Risk has been discovered
- First triage on this potential Security Issue
- A Security Risk has been confirmed
- Fix In Progress
- A Security Issue is being worked on
- Under review
- Security Fix is under review
- Fix accepted
- Security Fix has been accepted, and will be merged
- Embargoed disclosure
- This Security Issue has been Disclosed to a limited audience
- Public disclosure
- This Security Issue has been made public
- Not a security bug
- This is not a Security Issue
- Hardening opportunity
- This is not strictly a Security issue, but the issue can be hardened
- Not a bug
- This is not an Security Issue, nor a normal Issue.
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.
- Not a Bug
- Not Done
- Work has not been completed on this issue.