JIRA - Local help

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
Bug
A problem which impairs or prevents the functions of the product.
Improvement
An improvement or enhancement to an existing feature or task.
New Feature
A new feature of the product, which has yet to be developed.
New JIRA Project
A request for a new JIRA project to be set up
Question
A formal question. Initially added for the Legal JIRA.
RTC
An RTC request
TCK Challenge
Challenges made against the Sun Compatibility Test Suite
Task
A task that needs to be done.
Test
A new unit, integration or system test.
Wish
General wishlist item.
For Sub-Task Issues
Sub-task
The sub-task of the issue
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.

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 not closed can be reopened.
On Hold
The issue is open but work on it is temporarily suspended until further feedback is received determining its resolution.
Continued
The issue was on hold, and feedback was received indicating that further action are required towards its resolution.
Patch Available
A patch for this issue has been uploaded to JIRA by a contributor.
Patch Reviewed
A patch attached to this issue has been reviewed by another contributor.
Patch Revised
A patch attached to this issue has been revised by the contributor.
Patch Finalized
A patch attached to this issue is ready to be committed.
Ready To Review
Issue is to be reviewed before resolving/closing
Documentation Required
Documentation needs to be updated/created before resolving/closing the issue
Testcases Required
Further (unit and/or integration) test cases are required before resolving/closing the issue
Documentation/Testcases Required
Documentation and Test Cases must be created/updated before resolving/closing the issue
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.
Invalid
The problem isn't valid and it can't be fixed.
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.
Later
Later
Not A Problem
The described issue is not actually a problem - it is as designed.