API change with impact on API users
Something that is not needed anymore and can be cleaned up
Consulting (requiring support to solve a problem)
Discussion (enaging others in deciding about multiple options)
Enhancement, improvement, extension
Tracking or fixing a flaky test
Something that impedes developers, operators, users or others in their work
Proof of concept or prototype
Question (asking for help, advice, or technical detail)
Outage that requires root cause analysis after issues were mitigated (usually after downtime)
Bug that hit us already in the past and that is reappearing/requires a proper solution
Something that is only solved on the surface, but requires more (re)work to be done properly
Temporarily on hold (will not age; may have dependencies, lack priority, miss feedback, etc.)
Nobody worked on this for 12 months (final aging stage)
Nobody worked on this for 6 months (will further age)
Should not be merged via 'Squash and merge' to keep separate commits
Should be merged via 'Squash and merge'
Needs to be cherry-picked to older version
Needs (more) documentation
Needs help by someone else
Needs to keep the issue open, no auto close
Needs approval for merging
Needs approval for testing (check PR in detail before setting this label because PR is run on CI/CD)