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 Case
For Go2Group SYNAPSE Test Case issue type
Test Plan
For Go2Group SYNAPSE Test Plan issue type
For Sub-Task Issues
Subtask
Technical task
Created by JIRA Agile - do not edit or delete. Issue type for a technical task.
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.

Less Major
Oprioriterad
Just nu är ärendet inte klart för prioritering inför sprint-planering
Major
Major loss of function.
Trivial
Cosmetic problem like misspelt words or misaligned text.
Unnecessary
En test prioritering
Medium
Blocker
Blocks development and/or testing work, production could not run.
Minor
Minor loss of function, or other problem where easy workaround is present.
Critical
Crashes, loss of data, severe memory leak.
Less Minor

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.

To Do
In Progress
This issue is being actively worked on at the moment by the assignee.
Done

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
GreenHopper Managed Resolution
Won't Do
This issue won't be actioned.
Duplicate
The problem is a duplicate of an existing issue.
Declined
This issue was not approved.
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.
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.
Incomplete
The problem is not completely described.
Done/Klart
Work has been completed on this issue.
Won't Do/Inte göra
This issue won't be actioned.
Duplicate/Dubblett
The problem is a duplicate of an existing issue.
Declined/Nekad
This issue was not approved.
Inplanerad fix/Planned fix
Ärendet har eskalerats till utvecklingsärende och levereras enligt schema.