Drag to reorder prioritized labels and change their relative priority.
The enhancement proposal has been accepted.
This question has been answered. The actual answer should be included in the issue description in an “Answer” section.
This issue is an alleged or factual bug and describes a defective behavior, missing documentation, bad performance etc.
This task has been completed. The issue description should include the report on any relevant outcome of this task under the “Report” section or a link to a report.
If this is a documentation or specification issue the missing/inaccurate parts have been identified. If this is about behavior, the defect has successfully been reproduced.
This issue is a duplicate and will not be further processed. The preferential issue should be linked in the issue description.
This issue describes a new feature - that is new functionality or any other enhancement of the software.
This issue does not meet any standard or reasonable non-standard requirements to be further processed.
The assignees cannot proceed with their work for a lack of information. If the information is not given to them in due time this issue will be closed.
The assignee cannot proceed with this issue due to dependency on another issue which needs to be closed or at least reach a certain state first.
A proposed feature is to be discussed and further specified by the project team who then decides to accept or reject the proposal.
This issue is a question or a problem that can be answered by a person with enough information.
This feature proposal has been rejected. The decision should be explained in the issue description in the “Rationale” section.
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.
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.
Severity 1 - Blocker: Outage, broken feature with no workaround.
Severity 2 - Critical: Broken Feature, workaround too complex & unacceptable.
Severity 3 - Major: Broken Feature, workaround acceptable.
Severity 4 - Low: Functionality inconvenience or cosmetic issue.
A task is anything which does not fit into any other life-cycle and this particular state represents the uncompleted task.