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
Test
Represents a Test
Test Set
Represents a Test Set
Test Execution
Represents a Test Execution
Pre-Condition
Represents a Pre-Condition
Test Plan
Represents a Test Plan
Power Cord
Contact
Issue type for managing contacts.
License
Notebook
IT Help
For general IT problems and questions. Created by Jira Service Management.
Service Request
Created by Jira Service Management.
Service Request with Approvals
For requests that require approval. Created by Jira Service Management
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.
Incident
For system outages or incidents. Created by Jira Service Management.
Change
Created by Jira Service Management.
Problem
Track underlying causes of incidents. Created by Jira Service Management.
Work Contract
Human Resources Staff Pool - Work Contract Issue Type
Screen
Keyboard
Headphones
Location
Project
Issue type for managing projects.
Project Cluster
Issue type for managing project clusters.
Planning Interval
PI Objective
Initiative
Agile Release Train
SAFe Team
Support
For customer support issues. Created by Jira Service Management.
Printer
Issue type for managing printers.
Network Device
Issue type for managing network devices.
Task
A task that needs to be done.
Customer Requirement
Functional Requirement
Non-Functional Requirement
Test Case
Epic
Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.
Ethernet Cable
Test asset tpye
User
Zadanie to test
Custom issue type
Page
condition
Custom
Asset
Assets
for deleting 2
Password
Milestone
level1
USB Flash Drive
Company
Test Type 1
Test Type 2
Organization
Laptop
Server
Video projector
Telephone
Chair
Programming
Product
Other Hardware Type
Sofa
Virtual Server
Other Assets Type
Version
Component
Wardrobe
Release
Multimedia
Management System
Table
Other Software Type
External hard drive
Deal
Stand
Employee
Desktop
Operation Systems
Module
Person
Smartphone
Contract
Server Rack
Database
Application
Story
Created by Jira Software - do not edit or delete. Issue type for a user story.
Office
Implementation Incident
Test Type 3
Template
Issue Type for Templates
PR
For Sub-Task Issues
Sub Test Execution
Represents a Sub Test Execution
Sub-task N
Sub-Template
Sub-Issue Type for Templates
Sub-bug
Sub-task
The sub-task of the issue

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.

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.
Blocker
The problem will block progress.
Minor
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.

Open
The issue is open and ready for the assignee to start work on it.
Being Written
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 Review 2
A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.
Published!
The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
To Do
Done
Technical review
Inactive
Opportunity
Waiting for Order
In Proposal
In Delivery
In Order Confirmation
Declined
This was auto-generated by Jira Service Management during workflow import
Waiting for support
This was auto-generated by Jira Service Management during workflow import
Waiting for customer
This was auto-generated by Jira Service Management during workflow import
Pending
This was auto-generated by Jira Service Management during workflow import
Canceled
This was auto-generated by Jira Service Management during workflow import
Escalated
This was auto-generated by Jira Service Management during workflow import
Waiting for approval
This was auto-generated by Jira Service Management during workflow import
Work in progress
This was auto-generated by Jira Service Management during workflow import
Backlog
Selected for Development
Draft
Published
Archived
In Review
In repairment
Used
To purchase
Broken
Available
Awaiting CAB approval
This was auto-generated by Jira Service Management during workflow import
Planning
This was auto-generated by Jira Service Management during workflow import
Awaiting implementation
This was auto-generated by Jira Service Management during workflow import
Implementing
This was auto-generated by Jira Service Management during workflow import
Peer review / change manager approval
This was auto-generated by Jira Service Management during workflow import
Completed
This was auto-generated by Jira Service Management during workflow import
Under investigation
This was auto-generated by Jira Service Management during workflow import
Under review
This was auto-generated by Jira Service Management during workflow import
Leased to 3rd Party
Parental Leave
Onboarding
Sabbatical
Waiting for Onboarding
Offboarding
Drafting
Contract Ready
Waiting for Applicant
QA
In Development
License number exceeded
Expired
Entwurf/DRAFT
Fachliche Prüfung / prof review
Redaktionelle Prüfung / Editorial Review
Veröffentlicht / Released
Editorial Review
Closed
Resolved
This was auto-generated by Jira Service Management during workflow import
In Assessment
In Creation
In Test
In Migration
Uncommitted
Committed
Approved
Cancelled
Rejected
In progress
This was auto-generated by Jira Service Management during workflow import
Accepted
Final
New
Failed
Passed
To all

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.

Done
Work has been completed on this issue.
Won't Do
This issue won't be actioned.
Duplicate
The problem is a duplicate of an existing issue.
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.
Declined
This issue was not approved.
Known Error
The problem has a documented root cause and a workaround.
Hardware failure
Software failure