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
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
- A problem which impairs or prevents the functions of the product.
- Config Request
- A task or bug logged for development purposes. (Code review, etc)
- A big user story that needs to be broken down.
- An improvement or enhancement to an existing feature or task.
- New Feature
- A new feature of the product, which has yet to be developed.
- Security Review
- A problem identified by a security review.
- A task that needs to be done.
For Sub-Task Issues
- The sub-task of the issue
- Technical task
- A technical task.
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.
- Causes a serious crash, data corruption, or blocks use or testing of a major product feature without a workaround
- Serious problem affecting major functionality such as crashes, loss of data, severe memory leak with no workaround
- Major loss of function that is isolated to a specific feature and has a workaround
- Minor loss of function, or other problem where easy workaround is present.
- Cosmetic problem like misspelt words or misaligned text.
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.
- 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.
- This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.
- A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.
- The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
- This issue has been logged in the bug system
- Pending Closure
- A solution has either been delivered or the case has become inactive
- Waiting on Hyperic
- Waiting on a response from Hyperic
- Waiting on Customer
- Waiting on a response from Customer
- Internal: Waiting on Level 3
- Waiting on a response from Level 3
- Internal: Waiting on Support
- Waiting on a response from Support
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.
- A fix for this issue is checked into the tree and tested.
- The problem described is an issue which will possibly be considered at a later time.
- The problem is a duplicate of an existing issue.
- 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.
- Logged this issue in the HQ project
- The problem is invalid.
- This issue is hibernation and will be reviewed at a later time.