Needs to be resolved soon, because it impacts users negatively
Has no particular urgency
A few weeks of work or large change
A few days of work or medium change
A few hours of work or small change
A few minutes of work or very small change (usually trivial or cosmetic)
Issue was accepted as something we need to work on
Issue requires issue author action
Issue is blocked (e.g. because of dependencies)
Issue is closed (either delivered or triaged)
Issue has external dependency
Issue needs gardener guys attention
Issue is in delivery/deployment
Issue is in progress/work
Issue is new and unprocessed
Issue on hold (e.g. because work was suspended)
Issue is overdue (i.e. the allotted time expressed through `effort` lapsed)
Issue requires cluster owner action
Issue is under investigation
Gardener blocked, user must resolve a configuration problem
Issue is created because the cluster is in both a deletion and failed state
We have already a duplicate of this
We can ignore this (consequence of experimental usage)