JIRA Concepts — Issues

JIRA can be used to track many different types of issues. The default issues are listed below, but you can add your own at the administration section.

Bug

A problem which impairs or prevents the functions of the product.

New Feature

A new feature of the product, which has yet to be developed.

Task

A task that needs to be done.

Improvement

Not a new feature, rather an enhancement of an old one.

Custom Issue

This icon is used for your own custom issue types.

An issue has a priority level which indicates its importance. The default priority levels are listed below. In addition, you can add your own priority levels at the administration section.

Blocker

Blocks development and/or testing work.

Critical

Crashes, loss of data, severe memory leak.

Major

Major loss of function.

Minor

Minor loss of function, or other problem where easy workaround is present.

Trivial

cosmetic problem like misspelled words or misaligned text.

Each issue has a status, which indicates the stage of the issue. Issues generally start as being open, and then will progress to resolved and then closed. Depending on circumstances, it may also progress to the other statuses.

Open

This issue is in the initial 'Open' state.

In Progress

This issue is being actively worked on at the moment by the assignee.

Resolved

A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened and become reopened, are marked verified, or are closed for good and marked closed.

Reopened

This issue was once resolved, but the resolution was deemed incorrect. For example, a Cannot Reproduce issue is reopened when more information shows up and the issue is now reproducible. From here issues are either marked In Progress, Resolved or Closed.

Closed

The issue is considered dead, the resolution is correct. Any zombie issues who choose to walk the earth again must do so by becoming reopened.

An issue can be resolved in many ways, only one of them being "fixed". The default resolutions are listed below. You can also add your own in the administration section.

Fixed

A fix for this issue is checked into the tree and tested.

Won't Fix

The problem described is an issue which will never be fixed.

Duplicate

The problem is a duplicate of an existing issue. Marking an issue duplicate requires the issue# of the duplicating issue and will at least put that issue number in the description field.

Incomplete

There is not enough information to work on this issue.

Cannot Reproduce

All attempts at reproducing this issue were futile, or not enough information was available to reproduce the issue. Reading the code produces no clues as to why this behaviour would occur. If more information appears later, please reopen the issue.