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
-
IT Help
- For general IT problems and questions. Created by Jira Service Desk.
-
Service Request
- Created by Jira Service Desk.
-
Service Request with Approvals
- For requests that require approval. Created by Jira Service Desk
-
Bug
- A problem which impairs or prevents the functions of the product.
-
Task
- A task that needs to be done.
-
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.
-
Test
- This Issue Type is used to create Zephyr Test within Jira.
-
Story
- Created by Jira Software - do not edit or delete. Issue type for a user story.
-
Test Case
- A manual testing step
-
Epic
- Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.
-
Help Desk
- A help request sent to a Service Desk
-
New VM
-
LTR
- Long Time Request
-
New Key Feature
- A new feature of the product, which has yet to be developed.
-
Incident
-
QA testbed VM
- QA testbed VM
-
Problem
- Track underlying causes of incidents. Created by JIRA Service Desk.
-
Change
- For system upgrades or alterations. Created by JIRA Service Desk.
-
Access
- For new system accounts or passwords. Created by JIRA Service Desk.
-
Change request
- Change request
-
Fault
- Track system outages or incidents. Created by JIRA Service Desk.
-
Help
- Request help
-
Information
- General information
-
Information Request
-
New Documentation
-
Purchase
- Track items that need to be bought. Created by JIRA Service Desk.
-
Scheduled Maintenance
-
Security Vulnerability
- A security hole
-
Question
- A question e.g. how to do something.
-
Production Issue
- Any issue relating to the production instance
-
Config change
- A request of config change
For Sub-Task Issues
-
Patch
- Applying patch for the issue
-
Installation
- Installation of the software related with the issue
-
Research
- Technology research related with the issue
-
Development
- Code development related with the issue
-
Tests
- Tests of changes related with the issue
-
Documentation
- Preparation of documentation for the issue
-
Technical task
- A technical task.
-
General
-
MRLG
- MRLG
-
Sub-task
- The sub-task of the issue
-
LG
- LG
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.
-
Highest
- This problem will block progress.
-
High
- Serious problem that could block progress.
-
Medium
- Has the potential to affect progress.
-
Low
- Minor problem or easily worked around.
-
Lowest
- Trivial problem with little or no impact on progress.
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.
- Submitted
- 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.
- To Do
- Done
- Backlog
- Selected for Development
- In Review
- Declined
- This was auto-generated by Jira Service Desk during workflow import
- Waiting for support
- This was auto-generated by Jira Service Desk during workflow import
- Waiting for customer
- This was auto-generated by Jira Service Desk during workflow import
- Pending
- This was auto-generated by Jira Service Desk during workflow import
- Canceled
- This was auto-generated by Jira Service Desk during workflow import
- Escalated
- This was auto-generated by Jira Service Desk during workflow import
- Waiting for approval
- This was auto-generated by Jira Service Desk during workflow import
- Work in progress
- This was auto-generated by Jira Service Desk during workflow import
- Under Review
- Approved
- Cancelled
- Rejected
- In Test
- Ready To Test
- Created
- Deleted
- Running
- Suspended
- Turned off
- Need info
- On Hold
- The issue has been put on hold
- Postponed
- Re-work
- Review
- This status is managed internally by JIRA Software
- Ready for UAT
- This status is managed internally by JIRA Software
- Ready
- Awaiting Review
- A new test case that needs to be approved for use.
- Test
- This status is managed internally by JIRA Software
- Consolidated Testing
- This status is managed internally by JIRA Software
- Testing
- This status is managed internally by JIRA Software
- Awaiting CAB approval
- This was auto-generated by Jira Service Desk during workflow import
- Planning
- This was auto-generated by Jira Service Desk during workflow import
- Awaiting implementation
- This was auto-generated by Jira Service Desk during workflow import
- Implementing
- This was auto-generated by Jira Service Desk during workflow import
- Peer review / change manager approval
- This was auto-generated by Jira Service Desk during workflow import
- Completed
- This was auto-generated by Jira Service Desk during workflow import
- Under investigation
- This was auto-generated by Jira Service Desk during workflow import
- Waiting for third party
- Initiation
- Analysis
- Paused
- Verification
- Improvments check
- In Revirew
- This status is managed internally by Jira Software
- Open
- This was auto-generated by Jira Service Desk during workflow import
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.
- Invalid
- The problem described is actually not a probelm
- Implemented
- The request has been implemented
- Done
- Won't Do
- This issue won't be actioned.
- Declined
- This issue was not approved.
- Not A Bug
- The issue is not a bug
- Will not be fixed
- It was decided that the issue will not be fixed
- 1
- 1