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
Initiative
Groups epics together.
Epic
Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.
SUNET
NORDUnet
LIS
E-post
Ärenden som skapats via e-postmeddelande.
Extern
Supportfråga från externa användare
Intern
Supportfråga från intern användare
Supportfråga
Övrig supportfråga
Begäran
Chattkonversation
Uppgift/aktivitet
Uppgift
Ny funktion/förbättring
Generellt för att införa nya funktioner och förbättringar
Fel - användning
Något är fel på hur systemet används
Fel - systemfel
Något är fel på systemet
För bedömning
Servicedesk
Ärenden som hanteras inom servicedesk, te.x. incidenter och löpande justeringar.
Infrastrukturåtgärd
Förändringar i RUTs infrastruktur (OPS) som faller utanför ramarna för normal applikationsutveckling.
Registermodellering
Ärenden som behövs för att läsa in ett nytt register och få det redo för validering..
Registerförvaltning
Ärenden som behövs för att förvalta ett befintligt register.
Användarstöd
Service request new
Story
Created by Jira Software - do not edit or delete. Issue type for a user story.
System
Fel
Ett fel som ska åtgärdas
Scheduled
TEST
TEST
Unscheduled
Requirement
For Go2Group SYNAPSE Requirement issue type
Test Case
For Go2Group SYNAPSE Test Case issue type
Test Plan
For Go2Group SYNAPSE Test Plan issue type
Incident
For system outages or incidents. Created by Jira Service Desk.
Bug
A problem which impairs or prevents the functions of the product.
New Feature
A new feature of the product, which has yet to be developed.
Improvement
An improvement or enhancement to an existing feature or task.
Change
Created by Jira Service Desk.
Service Request with Approvals
For requests that require approval. Created by Jira Service Desk
Service Request
Created by Jira Service Desk.
IT Help
For general IT problems and questions. Created by Jira Service Desk.
Task
A task that needs to be done.
Problem
Track underlying causes of incidents. Created by Jira Service Desk.
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.

Critical
Crashes, loss of data, severe memory leak.
Blocker
Blocks development and/or testing work, production could not run.
Major
Major loss of function.
Highest
This problem will block progress.
High
Serious problem that could block progress.
Medium
Low
Minor problem or easily worked around.
Lowest
Trivial problem with little or no impact on progress.
Minor
Minor loss of function, or other problem where easy workaround is present.
Trivial
Cosmetic problem like misspelt words or misaligned text.
Not used
Unnecessary
En test prioritering
Less Major
Less Minor
Oprioriterad
Just nu är ärendet inte klart för prioritering inför sprint-planering

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.
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
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
Business Assessment
Technical Assessment
Processing
Decision
Awaiting Measure
Accepted
Establish
Active
Discontinued
Identify
Classified
Risk Management
Awaiting New Classification
Waiting
In Review
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
Under review
This was auto-generated by Jira Service Desk during workflow import
Opening
Backlog
Selected for Development
To Test
This status is managed internally by Jira Software
All
InProgress
Approved
in progress2
Awaiting external response
Planned
Öppnades på nytt
Tillagt för att funka med import från gamla Prisma JSD projektet PS.
Stängd
I test
Ärendet kan testas.
1:a linjen - Pågående
Arbete pågår i ärendet.
1:a linjen - Inkommen
Ärendet har inkommit till 1:a linjen och ska tilldelas/påbörjas.
1:a linjen - Lösning finns
2:a eller 3:e linjen har föreslagit en lösning på ärendet.
2:a linjen - Pågående
Arbete pågår i ärendet.
2:a linjen - Inkommen
Ärendet har inkommit till 2:a linjen och ska tilldelas/påbörjas.
Paus svar-SLA (2:a)
SLA "Time to response" pausas.
Hotfix
Pausad
För att pausa "Time to resolution", om ärendet väntar in något under längre tid.
Paus svar-SLA (1:a)
SLA "Time to response" pausas.
Väntar på godkännande
This was auto-generated by Jira Service Desk during workflow import
3:e linjen - Inkommen
Ärendet har inkommit till 3:e linjen och ska tilldelas/påbörjas.
Resolved by 2nd line
2:a linjens support
In SAT-test
This issue is resolved but pending for external test.
Implemented
Something is implemented
In Prod-test
In Prod-test
Incomplete
Incomplete
Deploy to Prod
Rejected
Bug not approved
Todo
Idé har kommit in
Code review
Test
Implementation pågår
Test pågår
Implementation i testmiljö pågår
Test att ny implementation är korrekt via en testmiljö
Escalated external
Ready for test
Granskning pågår
Done in development
The issue is implemented, code reviewed and tested in isolation. The issue can now be transferred to QA.
Awaiting internal response
Rejected by 2nd line
Verifiering ej godkänd
Waiting for prod
Verifiering pågår

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.