Jira - Local help - Jira

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

Defect (bug): A problem which impairs or prevents the functions of the product.
Story: Created by Jira Software - do not edit or delete. Issue type for a user story.
New feature (RFE): A new feature of the product, which has yet to be developed.
Task: A task that needs to be done.
Improvement: An improvement or enhancement to an existing feature or task.
Defect (bug) by email: A defect reported by email
New Feature: A new feature of the product, which has yet to be developed.
Bug: A problem or error.
Epic: 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

Sub-task

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: Blocks development and/or testing work, production could not run.
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 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.

Submitted: The issue is open and ready for the assignee to start work on it.
Resolution 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.
Resolved, to be confirmed: A resolution has been taken, and it is awaiting verification by reporter.
Closed: The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
Enhancement, acknowledged: All parties acknowledge this issue is a Request For Enhancement.
Defect, reproducible: The defect is reproducible by the developers.
Enhancement, Specs ready: The specifications for a Request For Enhancement have been written.
Effort estimate ready: The effort estimate for an enhancement is ready.
Defect, acknowledged: All parties acknowledge this issue is a defect (bug).
Test ready: A test for reproducing the issue is ready.
Defect, cause understood: The cause of a defect has been understood by developers.
Enhancement, approved: An enhancement has been approved.
Resolution under test: The resolution for an issue is being tested.
Can't be reproduced: The developers can't reproduce the defect.
Defect, under investigation: Developers are investigating the causes of a defect.
Building: Source code has been committed, and JIRA is waiting for the code to be built before moving to the next status.
Build Broken: The source code committed for this issue has possibly broken the build.
To Do
In Progress
In Review
Done

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.

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.
Incomplete: The problem is not completely described.
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.
Done: Work has been completed on this issue.
Won't Do: This issue won't be actioned.