Skip to content
Labels can be applied to issues and merge requests. Group labels are available for any project within the group.

Labels

  • 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.
  • 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 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.
  • A task is anything which does not fit into any other life-cycle and this particular state represents the uncompleted task.
  • Severity 4 - Low: Functionality inconvenience or cosmetic issue.
  • Severity 3 - Major: Broken Feature, workaround acceptable.
  • Severity 2 - Critical: Broken Feature, workaround too complex & unacceptable.
  • Severity 1 - Blocker: Outage, broken feature with no workaround.
  • 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.
  • 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.
  • This issue is a question or a problem that can be answered by a person with enough information.
  • This issue is performance related
  • Priority: 3 (Low)
  • Priority: 2 (Medium)
  • Priority: 1 (High)
  • 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.
  • This issue can in principle be resolved by newcomers without any specific experience in developing CaosDB
  • 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.
  • This issue does not meet any standard or reasonable non-standard requirements to be further processed.