Guides
Issue to done
The path of a ticket from intake to closure.
A concern is recorded as an issue, assigned to the right person, worked on, reviewed and closed.
Who is involved
Section titled “Who is involved”Whoever reports the issue (any role), the person working on it (Employee, Engineer) and, for triage and review, Team lead or Project manager.
Prerequisites
Section titled “Prerequisites”None in particular. A project is optional.
The workflow
Section titled “The workflow”- Record – In Issues or My issues create a new issue: title, description, and if needed priority, due date, labels and project. It starts as „Entwurf“ (Draft).
- Classify (triage) – In Issues you review new issues, for example grouped by assignment or state. You set priority and assignment and put the issue to „ToDo“. Large concerns are split into sub-issues.
- Work on it – The assigned person sees the issue in My issues and sets it to „In Bearbeitung“ (In progress). Questions go through „Kommentare“ (Comments). Involved people add themselves as subscribers.
- Optionally delegate – Via „Delegieren“ (Delegate), Polaris or an AI agent takes over. You see the progress in the „Agent-Protokoll“ (Agent log) (see Agents).
- Review – Once the work is finished, the issue goes to „in Prüfung“ (In review). The reviewer gives feedback via comments or closes it.
- Close – State „Erledigt“ (Done). If the concern is already recorded elsewhere, choose „Duplikat“ (Duplicate). If it will not be implemented, choose „Fehlgeschlagen“ (Failed).
Every change appears under „Aktivität“ (Activity). This keeps the history traceable.
Result
Section titled “Result”The issue is closed, and the history is documented. It counts in the Overview under „Erledigt (7 T)“ (Done (7 d)).