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
Information
Request for explanation of functionality or information to the Support Center.
Risk
For use with the Risk Register
Hardware Failure
The hardware equipment is not working properly or as expected.
Purchase
Track items that need to be bought.
Change
For system upgrades or alterations.
Fault
Track system outages or incidents.
Access
For new system accounts or passwords.
Testing
Issues concerning testing the functionality.
IT Help
For general IT problems and questions.
Implementation
Tasks concerning the implementation of the agreement implementation.
Service
Issues concerning servicing.
Bug
A problem which impairs or prevents the functions of the product.
Epic
Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.
Story
Created by Jira Software - do not edit or delete. Issue type for a user story.
New Feature
A new feature of the product, which has yet to be developed.
Task
Issues that require workload assessment and Customer acceptance.
Improvement
An improvement or enhancement to an existing feature or task.
Implementacja
Implementacja
Support
For customer support issues. 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
For Sub-Task Issues
Sub-Task
Issues that consist a part of a Parent Issue
Technical Task
A technical 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.

Critical
Reaction must be immediate because the problem completely prevented further work.
High
The problem must be solved quickly because of the functionality does not work but it is possible to continue to work after bypass.
Medium
The problem is not serious and does not cause downtime.
Low
Additional features or request for information.

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, ready to be assigned and to start working 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 cannot be reopened.
Reconciled
The issue has been reconciled and is invoiced.
Conception
The idea is being prepared in the concept of how the issue should be addressed.
For Acceptance
The issue was scheduled, was given time and is waiting for approval by the client.
Accepted
Commercial terms of the issue has been accepted by the client and can begin work.
Forwarded
The issue was forwarded to the vendor. Further work is being withheld pending a response.
Verification
The issue has been completed and its verification is needed by the customer that they can be settled.
Ready For Billing
The issue is ready for settlement.
In QA Review
Issue has been resolved but needs to be verified by QA Team and finally accepted before release.
Waiting for Customer
Issue waits for response from the customer and no work is done.
Test Preparation
Preparation of automated test.
Test Run
Run of test automation.
Waiting for Triage
Issue has been accepted and forwarded to development for bug-fixing or new feature implementation.
Waiting for support
This was auto-generated by JIRA Service Desk during workflow import
Analyzed
The impact and probability of the risk have been specified
Treated
The treatment of the risk has been specified
Declined
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
Work in progress
This was auto-generated by JIRA Service Desk during workflow import
Done
This was auto-generated by JIRA Service Desk during workflow import
To Do
Doc in progress
The documentation for the customization is being actively prepared.
Doc for acceptance
The documentation for this customization was prepared and is waiting for approval by the client
Doc Accepted
The conception of the customization has been accepted by the client and can begin work.
Development
This customization is being actively worked on by the Dev Team
Quote for Acceptance
The castomization was scheduled, was given time and is waiting for approval by the client
Quote accepted
The quotation for the cutomization was given and has been accepted by the client, the work can begin.
Waiting for approval
This was auto-generated by Jira Service Desk during workflow import
Anulowany
Zatwierdzony
Odrzucony
Waiting for prepayment
Issue is waiting for prepayment settlement
Prepayment received
Prepayment has been received
To Merge
AM. In QA Review
Under Review
Approved
Cancelled
Rejected

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
The issue has been successfully completed, it is proven and tested.
Cannot Reproduce
All attempts at reproducing this issue failed, or not enough information was available to reproduce the issue. If more information appears later, please reopen the issue.
Duplicate
The problem is a duplicate of an existing issue.
Incomplete
The problem is not completely described.
Obsolete
The issue is already outdated and will not be further continued.
Won't Do
This issue won't be actioned.
Declined
This issue was not approved.
Known Error
The problem has a documented root cause and a workaround.
Hardware failure
Software failure