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
- Konzept
- Konzept oder Aufwandsschätzung
- Meeting
- Meeting, Telko, Jour-Fixe usw.
- Frage
- Nicht im Projekt
- Änderung
- Eine Änderung an bestehenden Features.
- Initiative
- Aggregates multiple Epics
- Epic
- Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.
- Fehler
- Ein zu behebender Fehler.
- Neues Feature
- Ein neu zu implementierendes Feature.
- Story
- Created by Jira Software - do not edit or delete. Issue type for a user story.
- Tätigkeit
- Eine zu erledigende Aufgabe oder Tätigkeit.
- Verbesserung
- Eine Verbesserung eines bereits implementierten Features.
- 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.
- Bug
- A problem which impairs or prevents the functions of the product.
- Task
- A task that needs to be done.
For Sub-Task Issues
- Sub-task
- The sub-task of the issue
- Teilvorgang
- Ein Teilvorgang des gesamten Vorgangs.
- Technische Aufgabe
- Eine technische Aufgabe.
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.
- Blocker
- Blockiert die Entwicklung und/oder die Produktivumgebung.
- Kritisch / Critical
- Abstürze, Datenverluste oder erheblicher Speicherverbrauch.
- Hoch / Major
- Große Auswirkungen.
- Mittel / Medium
- Mittlere Auswirkungen.
- Niedrig / Minor
- Geringe Auswirkungen.
- Trivial
- Kosmetische Probleme, z.B. falshc geschriebene Wörter.
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.
- Offen / Open
- Der Vorgang ist offen zur Bearbeitung.
- Unter Bearbeitung / In Progress
- Der Vorgang ist derzeit unter Bearbeitung.
- Neu geöffnet / Reopened
- Der Vorgang wurde neu geöffnet.
- Gelöst / Resolved
- Der Vorgang wurde bearbeitet.
- Geschlossen / Closed
- Der Vorgang wurde abgeschlossen.
- Review Me
- Der Vorgang benötigt das Review eines weiteren Projektbeteiligten.
- Test Me
- Der Vorgang muss vom Testbeauftragten gestestet werden.
- Accept Me
- Der Vorgang muss vom Productowner abgenommen werden.
- Merge Me
- Der Vorgang muss vom Bearbeiter in alle relevanten Branches gemerged werden.
- Waiting
- This status is managed internally by JIRA Software
- To Do
- In Progress
- In Review
- Done
- Backlog
- Selected for Development
- Release Me
- Für diesen Vorgang muss noch (auf mindestens einem Branch) ein Release erstellt werden.
- Merge Review
- Merge Test
- Merge In Progress
- Deploy Me
- Der Vorgang muss ausgerollt / installiert werden.
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 fixed.
- Duplicate
- The issue is a duplicate of another issue.
- Won't Do
- The issue will not be actioned.
- Shelved
- The issue will not be actioned in the forseeable future.
- Cannot Reproduce
- The issue cannot be reproduced.
- Incomplete Description
- The issue has not been described in enough detail.
- Not a Bug
- The issue is not a bug.