Jira Concepts - Issues

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
Aufgabe
Eine Aufgabe, die erledigt werden muss.
New Feature
A new feature of the product, which has yet to be developed.
Bug
Ein Problem, das die Funktionen des Produkts beeinträchtigt oder verhindert.
Task
A task that needs to be done.
Verbesserung
Eine Verbesserung oder Erweiterung zu einer bestehenden Funktion oder Aufgabe.
Neue Funktion
Eine neue Produktfunktion, die noch entwickelt werden muss.
Improvement
An improvement or enhancement to an existing feature or task.
GitHub Issue
Feature Request
Feature Request
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.
For Sub-Task Issues
GitHub Subtask
Sub-task
The sub-task of the issue
Unteraufgabe
Die Unteraufgabe des Vorgangs

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.

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
Backlog
Selected for Development
Archiviert
asdasd
Developement
Review
Finished
Testing
Approved
Deployed
Bugs
Code Review
Off The Records
IDEAS
EPIC: Content Service
TERMINE
Jans Wunderwelt
GitHub Issues (external / OpenSource)
Priorities/ Backlog
EPIC: Dockerization
EPIC: File Storage
EPIC: Calendar Service
NEXT PRIORITIES
EPIC: Kursseite
EPIC: Service ID Resolver
EPIC: Hausaufgaben
EPIC: Themen-Editor
EPIC: News
EPIC: UX improvements
READY
Meinel & Demofeatures
Top 20: PRIORITÄT
TO BE DAILY'D
RELEASE: #Lazurite (v0.12.0)
RELEASE: #Amethyst
RELEASE: User Stories
In Review
Under Review
Dieser Status wird intern von JIRA Software verwaltet
READY FOR DEVELOPMENT
Ready - genug Infos da
In Development
Dieser Status wird intern von JIRA Software verwaltet
In SC implementiert
Dieser Status wird intern von JIRA Software verwaltet
Ready - nötige Infos da
Discarded - Verworfen
Ready for Review
Gelistet
In Prüfung (Content)
In Kommunikation (Content)
In Vertrtagsverhandlung (Content)
Vertragsentwurf (Content)
Datenschutz-Prüfung (Content)
Vertragsabschluss (Content)
Für Ideenboard
First Level Support
Second Level Support
Muss entwickelt werden
Lösung kommunizieren

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.

Fertig
Die Arbeit für diesen Vorgang wurde abgeschlossen.
Reicht nicht
Dieser Vorgang wird nicht ausgeführt.
Duplikat
Das Problem ist ein Duplikat eines bestehenden Problems.
Kann nicht reproduziert werden
Alle Versuche, dieses Problem zu reproduzieren, sind fehlgeschlagen, oder zur Reproduktion des Problems waren nicht genügend Informationen verfügbar. Das Lesen des Codes ergab keine Hinweise auf die Ursache dieses Verhaltens. Wenn sich zu einem späteren Zeitpunkt mehr Informationen ergeben, öffnen Sie diesen Vorgang erneut.
Done
GreenHopper Managed Resolution
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.