Labels

The issue has been picked up for work by a developer in the team and the developer started to work on actively on the issue.

In testing

This is the first step of the process. Issue has been recently opened. Product team will identify/evaluate the following: - Clarify questions if required / verify DoR for Product is met. - It’s been identified if Design work is required or not. - Technical Feasibility - Components involved. - Team to work on that issue. - Severity (in case the issue refers to a bug)

A blocker has been identified and work cannot continue.

This label indicates that the issue affects Safari devices.

Issue is reproducible

Proof of Concept - issues necessary for potential customer acquisition. Can be scoped by deadline for planned presentations

Issues which are in the competence area of the frontend chapter. It is not a scoped label anymore as issues can be part of different chapters. Before we can start implementing/changing this, we need a UI/UX design first.

Issues which are in the competence area of the infrastructure chapter. It is not a scoped label anymore as issues can be part of different chapters.

Issues which are in the responsibility of the product team.

A software bug is an error, flaw or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways.

A task about creating or improving the UI/UX design