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
Epic
Created by JIRA Software - do not edit or delete. Issue type for a big user story that needs to be broken down.
Bug
A problem which impairs or prevents the functions of the product.
New Feature
A new feature of the product, which has yet to be developed.
Story
Created by JIRA Software - do not edit or delete. Issue type for a user story.
Task
A task that needs to be done.
Improvement
An improvement or enhancement to an existing feature or task.
User Documentation
Configuration Change
A request to track configuration changes in production
Delete Configuration Element
Add Configuration Element
Add a new configuration element
Question
On Call
On Call Intervention (during working hours or out of working hours)
Email
Issue Created by email to be classified manually.
Project Request
Hardware Replacement
Suggestion
Hardware Procurement
Firmware update
Incident
Information Request
Test
Upgrade
Upgrade task ( so far only used by the SCD project)
Publication
Intervention
Measurement
A task that is related to Measurements
R&D
A task that is related to R&D
Calibration
A task that is related to equipment calibration
Service & Maintenance
A task that is related to equipment service and maintenance
Out of Order
A piece of equipment is out of order
PLC License Request
A PLC related project license request
Release request
Add Test Templates
Add a skeleton testing directory to a Puppet manifest
CAD
3D design
Simulation
Support
PVSS License Request
PVSS License Request (EN-ICE)
SBS Call
Standby Service Call
LabVIEW License Request
National Instrument LabVIEW license request (EN-ICE-MTA)
New Installation or Feature
HW: new installation, SW: new feature
SBS notification
Patch
For Sub-Task Issues
Sub-task
The sub-task of the issue
Technical task
A technical task.
Improvement sub-task
A small improvement sub-task
Sub-test
Bug sub-task
A small bugfix

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.

Needs Decision
Mark an issue as needing a decision
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

Status Categories

Helps identify where an issue is in its lifecycle.
Issues move from To Do to In Progress when work starts on them, and later move to Done when all work is complete.

Done

Represents anything for which work has been completed

In Progress

Represents anything in the process of being worked on

No Category

A category is yet to be set for this status

To Do

Represents anything new

Issue 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 closed can be reopened.
In Testing
Failed
There was some effort to resolve it, but due to some circustances it cannot be done or repeated.
Waiting for 3'rd party
The team handling the issue are waiting for an action by 3'rd party (supplier, other organizational unit etc)
Waiting for Review
This issue is waiting for code review
Broken
The change is currently breaking something in testing
Rejected
The code review or testing process rejected the software change
In Review
This status is managed internally by JIRA Software
Approved
Monitoring
The issue is monitored to check it has been properly fixed
Prepare
Needs preparation
Done
To Do
On Hold
Needs information
More information is needed to proceed with this issue
Cancelled
Issue cancelled, no longer pursued
Validation by Client
Issue waiting for validation
Request ready
Request ready for analysis and approval
In QA
The issue has been merged into QA
Published
Pending Change Request
Delegated to External Expert
Postponed at ETM
Accepted
Fixed but not tested
Pending Change Request - 2
On QA
On Test
On-Hold
Blocked
Code Review
Testing
Backlog
Pending Deployment
This status is managed internally by JIRA Software
Ready for Test (Dev)
This status is managed internally by JIRA Software
Ready for Test (Test)
This status is managed internally by JIRA Software
Ready for Review
This status is managed internally by JIRA Software
Implementation Complete
This status is managed internally by JIRA Software
Pre-test Failed
Tag Requested
Tag Validating
Ready for Deployment
This status is managed internally by JIRA Software
Ready to Review/Test
This status is managed internally by JIRA Software
Being Reviewed/Tested
This status is managed internally by JIRA Software
Selected for Development
testo
This status is managed internally by JIRA Software
tesrta
This status is managed internally by JIRA Software
Duplicate
Assigned
Built
Verified
DR
This status is managed internally by JIRA Software
MS TA
This status is managed internally by JIRA Software
MS TA Completed
This status is managed internally by JIRA Software
MS Bid Preparation
This status is managed internally by JIRA Software
Out for Bid
This status is managed internally by JIRA Software
Bid Analysis
This status is managed internally by JIRA Software
IT TA
This status is managed internally by JIRA Software
IT TA Completed
This status is managed internally by JIRA Software
IT Dispatch Preparation
This status is managed internally by JIRA Software
IT Sent
This status is managed internally by JIRA Software
Selection
This status is managed internally by JIRA Software
Contract Edition
This status is managed internally by JIRA Software
Contract Sent
This status is managed internally by JIRA Software
Invalid
Being Tested TEST
This status is managed internally by JIRA Software
Test OK (DEV)
This status is managed internally by JIRA Software
Test OK (TEST)
This status is managed internally by JIRA Software
Being Tested (Test)
This status is managed internally by JIRA Software
Being Tested (Dev)
This status is managed internally by JIRA Software
MS-IT a charger dans CFU
This status is managed internally by JIRA Software
IT Archive
This status is managed internally by JIRA Software
Under Approval
This status is managed internally by JIRA Software
Work Order Analysis
This status is managed internally by JIRA Software
Measurement preparation
This status is managed internally by JIRA Software
Measurement on-going
This status is managed internally by JIRA Software
Measurement Completed
This status is managed internally by JIRA Software
Work Order Submitted
This status is managed internally by JIRA Software
Work Order Closed
This status is managed internally by JIRA Software
Report under Approval
This status is managed internally by JIRA Software
En Analyse
This status is managed internally by JIRA Software
Pending
This status is managed internally by JIRA Software
Doing
En redaction
This status is managed internally by JIRA Software
Ok Circulation
This status is managed internally by JIRA Software
En verification
This status is managed internally by JIRA Software
En follow-up
This status is managed internally by JIRA Software
En revision
This status is managed internally by JIRA Software
En validation
This status is managed internally by JIRA Software
tuend
This status is managed internally by JIRA Software
En dispatch
This status is managed internally by JIRA Software
Dispatched
This status is managed internally by JIRA Software
tue
getan
abgeschlossen
nicht zufrieden
Production Ready
This status is managed internally by JIRA Software
License Generation In Progress
PVSS license genetration in progress

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
Moved
Issue created in another project for ongoing development. Tracking continues there.
Not a Bug
The issue was reported as a bug but in fact that was the intended behaviour of the product. (It's not a bug, it's a feature!)
Work in progress
Work in progress
Unresolved
Fixed - Not deployed
A fix for this issue is checked into the tree and tested but not deployed
Fixed - Deployed
A fix for this issue is checked into the tree and tested
Postponed
The item will be fixed later (no date given)
Remind
TestFix
None
Need Info
Invalid
Done, untested
Done, untested
Fixed, waiting for confirmation
Fixed, waiting for confirmation
Confirmed
Confirmed
Fixed, waiting for release
Fixed, waiting for release
Done, Waiting for release
Done, Waiting for release
Done, waiting for confirmation
Done, waiting for confirmation
Cancelled
Won't Do
This issue won't be actioned.