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.

Bug
A problem which impairs or prevents the functions of the product.
Development Query
Questions regarding how to develop JBI artifacts (BC, SA, SU, SE, SL)
Epic
A big user story that needs to be broken down.
Feature Request
Request new features or suggest modifications to existing features.
Improvement Request
An improvement or enhancement to an existing feature or task.
New Feature
Ask for a new feature of the product to be developed.
Problem Report
A problem which impairs or prevents the functions of the product.
Question
Ask a question
Story
An user story
Task
A task that needs to be done.
Usage Query
General questions regarding how the product should be setup to achieve a particular goal

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.

|unused-0|
The issue is open and ready for the assignee to start work on it.
In Correction
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.
In Validation
A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.
In Checking
New
Issue was just created.
Inaccurate
Some information needed to reproduce/qualify the bug is missing.
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.
Resolved
The issue is considered resolved.
Closed
The issue is considered finished, the resolution is correct.
Need Information
Some information needed to reproduce/qualify the bug is missing.
Petalslink Investigating
Petalslink is currently investigating and working on this issue.
Inactive - Pending Closure
Issues we haven't heard back from the customer in a while, about to close.
Waiting For Customer
We are waiting on the customer to provide us with information.
Awaiting Product Fix
A fix is in the process of being implemented or deployed

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.

Answered
The question has been answered.
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.
Completed
The task has been completed.
Customer Timeout
If there has not been a response from the customer within six weeks, we assume the issue has been resolved locally
Duplicate
The problem is a duplicate of an existing issue.
Fixed
A fix for this issue is checked into the tree and tested.
Incomplete
The problem is not completely described.
Not a bug
The reported behaviour is as expected.
Resolved Locally
Issue was resolved locally by a workaround.
Special
A special support case.
Superseded
Issue has been made irrelevant by a later issue.
Timed Out
Details presumed obsolete due to prolonged issue inactivity.
Training Suggested
Petalslink has suggested a training course.
Unsupported Environment
The execution environment is not supported.
Won't Fix
The problem described is an issue which will never be fixed.