Jira Concepts - Issues

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
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.
Bug
A problem which impairs or prevents the functions of the product.
Epic
A big user story that needs to be broken down. Created by JIRA Software - do not edit or delete.
Story
A user story. Created by JIRA Software - do not edit or delete.
Task
A task that needs to be done.
Unforeseen story
Contract support
Deployment
Minichange
Finetuning
Code review
Service
Work incident
Plan request
Account management
Commitment
Administration
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.
24h
Solve within 24 hour

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.

Waiting for answer
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.
Ready for deploy
Closed
The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
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.
Test
To do
New
Assign
Code review & devtest
Done
Plan
In deze fase wordt een plan gemaakt voor het oplossen van dit issue: zoeken naar bron/oorzaak o.b.v. analyse van data + vinden van oplossing.
Verify
Verification by reporter
Make offer
Hour estimate / confirmation
Require client decision
Verify offer
Plan resources
Administrate
Assign (max 2 hour)
Max 2 hour triage
Re-choose hour allowance
Waiting for test deploy
Customer test
Investigate customer response
Blocked
Ready for client test
In Review
Invent
Draft
Verify specs
Waiting for client confirmation
Ready for delivery
Refinement
Delayed client test
Backlog
Selected for Development

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
Won't Do
This issue won't be actioned.
Planning planned
Planning declined
Commitment accomplished
Commitment failed
Commitment cancelled by client
Canceled