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.
Sales Support
New Feature
A new feature of the product, which has yet to be developed.
Risk
Requirement
Test
Research
A piece of research that is scheduled and tracked.
Suggestion
Public suggestions
User Story
Created by Jira Software - do not edit or delete. Issue type for a user story.
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.
Task
A task that needs to be done.
Story
Created by Jira Software - do not edit or delete. Issue type for a user story.
For Sub-Task Issues
Change Request
A schedulable change to a Requirement
Sub-task
The sub-task of the 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.

Not Evaluated
Not yet evaluated/prioritized
P0: Blocker
MUST be fixed ASAP. This includes issues that prevent/block further Qt development; Legal issues & Serious data loss issues.
P1: Critical
Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
P2: Important
Urgent, should be fixed, but will not stop the release.
P3: Somewhat important
Should be fixed, but doesn't affect the release in any way.
P4: Low
Would be nice to fix, but it's not very important.
P5: Not important
Not relevant and not urgent.

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.

Reported
The issue has been reported, but no validation has been done on it.
Need More Info
More information is needed to be able to proceed
Open
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
The issue is considered finished. Issues which are closed can be reopened.
Closed
The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
Implemented
The issue is fully implemented and ready for customer acceptance.
Verified
The issue has been verified.
Withdrawn
Released issue is withdrawn from release and is no longer supported.
Done
To Do
To be done
Blocked
The issue is being blocked by some impediment
Marketing review
This status is managed internally by JIRA Software
Technical review
This status is managed internally by JIRA Software
To Review
This status is managed internally by JIRA Software
Published
This status is managed internally by JIRA Software
Needs Review
This status is managed internally by JIRA Software
Select topic
This status is managed internally by JIRA Software
Writing
This status is managed internally by JIRA Software
Backlog
Ready for Development
Parking lot for Requests that are waiting for development.
Cancelled
Writing Outline
Platform Onboarding
Integration
Parking lot for any request that passed testing, before moving to production.
Design
Create Functional design for the request, find out business priority, find out answers to all the pending questions.
Analysis
More information about the request is collected from the requestor.
Testing
Request is ready for business user or someone else who has been assigned to start testing.
In Development
This issue is being actively developed at the moment by the assignee.
In Review
The issue is mostly waiting for code reviews. The assignee is still responsible for progress being made

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.
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 not a problem, e.g. wrong assumptions about expected behaviour being made.
Done
Work has been completed on this issue.
Won't Do
This issue won't be actioned.
Out of scope
The issue will not be resolved.
Moved
Not our problem - Moved it for some other group to handle