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. Below are the types configured in your system. More can be added from 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.
-
Task
- A task that needs to be done.
For Sub-Task Issues
-
Sub-task
- The sub-task of the issue
Priority Levels
Statuses
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.
|