Complexity E

Complexity D

Complexity C

Complexity B

Complexity A (Reference: Change a typo without API change.)

Severity 4 - Low: Functionality inconvenience or cosmetic issue.

Severity 3 - Major: Broken Feature, workaround acceptable.

The issue describes unwanted behavior which is produced by outdated/non- compliant/erroneous/unratable third-party software or it describes something that is not a defect in the first place.

The performance problems or defective behavior cannot be reproduced even though the information in the issue seems to be complete or the allegedly missing documentation or spefication is available, accurate and complete.

A task is anything which does not fit into any other life-cycle and this particular state represents the uncompleted task.

The triage is the state before any life-cycle begins. The assigned triagers decide which kind of issue is in front of them and hence which life-cycle the issue should to follow.

The feature or bug fix has been impleted, documented where necessary and tested by the developer and is now under review. This label should be removed after the last reviewer has reviewed the proposed resolution.

This issue is a question or a problem that can be answered by a person with enough information.

An unconfirmend bug is a bug that has not been confirmed yet.

When an issue is worked on due to a (paid) order, no matter whether the payment is per hour or fixed.

Severity 2 - Critical: Broken Feature, workaround too complex & unacceptable.

Severity 1 - Blocker: Outage, broken feature with no workaround.

The feature or bug fix is implemented, tested and documented if necessary and has successfully been reviewed. It can be included into the next release.

This feature proposal has been rejected. The decision should be explained in the issue description in the “Rationale” section.

A proposed feature is to be discussed and further specified by the project team who then decides to accept or reject the proposal.