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.

Defect
A problem which impairs or prevents the functions of the product.
Enhancement
An improvement or enhancement
Feature
A new feature
Task
A task that needs to be done.

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.

Blocker
Ignore these names and assume only relative priority
Critical
Ignore these names and assume only relative priority
Major
Ignore these names and assume only relative priority
Minor
Ignore these names and assume only relative priority
Trivial
Cosmetic problem like misspelt words or misaligned text.

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.
Ready for Screening
A patch has been attached to the issue, and is ready to be screened for quality / completeness / applicability.
Screened
An attached patch has been screened, and is ready to be applied by the project lead(s).
Accepted
The screened patch has been verified by the project owner, and is ready to be committed.
Vetted
The issue has been vetted, and is approved for work.
Triaged
Used by screeners to flag something for BDFL's attention

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.

Completed
Task completed
Declined
This task does not fit the project roadmap
Duplicate
The ticket duplicates another
Not Reproducible
Issue described cannot be reproduced