Skip to content
Matthias Ronge edited this page Nov 4, 2020 · 11 revisions

ℹ️ As of November 3, 2020. Issues recorded up to № 4,087. ✓ = linked branch awaiting merge. Solved.

⚠️ This classification is highly subjective.

10 Dangerous

A risk of life or limb, property damage, security issue or the risk of loss of work.

9 Unusable

An essential functionality of the application is not given. There is no work-around.

8 Faulty

A target functionality is not given.

7 Fragile

An error is badly intercepted. A tiny incorrect operation leads to bad things.

6 Unsightly

Slipped layout, typographical errors, …

5 Inconvenient

A target functionality is not available, but there is a work-around. Likewise: A target functionality can only be achieved with an unnecessarily high operating effort.

4 At a loss

Poor operator guidance, the meaning of input elements is not revealed, nothing seems to happen when a function is triggered (if the function actually works). Likewise: No error message in the event of an error, it gives the impression that the function has worked where it did not.

3 Opaque

Confusing program code, cleaning up necessary.

2 Non-interoperable

An in-house solution is used where a standard solution could be used.

1 New feature

A completely new type of functionality is desired.

0 Conception

Discussion with an open outcome, no clear goal yet.

Clone this wiki locally