GitLab

Labels

• hasEffort:High
  Effort labels reflect the expected workload. Based on the expectations of the work group. (Old label name: MAJOR)

  • Issues
  ·
  • Merge requests

  Simulation
• hasEffort:Low
  Effort labels reflect the expected workload. Based on the expectations of the work group. (Old label name: PATCH)

  • Issues
  ·
  • Merge requests

  Simulation
• hasEffort:Medium
  Effort labels reflect the expected workload. Based on the expectations of the work group. (Old label name: MINOR)

  • Issues
  ·
  • Merge requests

  Simulation
• isStatus:Duplicate
  This issue has already been raised or was already solved in another issue. Status labels reflect the current phase of an issue. Status labels can change. Old status label shall be removed. (Old label name: Duplicate)

  • Issues
  ·
  • Merge requests

  Simulation
• isStatus:WontBeFixed
  This label indicates that the task described in the issue will not be solved. Status labels reflect the current phase of an issue. Status labels can change. Old status label shall be removed. (Old label name: WontFix)

  • Issues
  ·
  • Merge requests

  Simulation
• isType:Bug
  This label indicates an issue that contains contradictions or errors in the standard. Type labels display the intended field of the issue. Type labels are static and never change. (Old label name: Bug)

  • Issues
  ·
  • Merge requests

  Simulation
• isType:GeneralQuestion
  General questions about the documentation, work-flow or anything related to the standard. Type labels display the intended field of the issue. Type labels are static and never change. (Old label name: GeneralQuestion)

  • Issues
  ·
  • Merge requests

  Simulation
• isType:InternalReview
  This label indicates that the issue was created during and as a result of the internal project review phase. Type labels display the intended field of the issue. Type labels are static and never change. (Old label name: Review)

  • Issues
  ·
  • Merge requests

  Simulation
• isType:NewFeature
  This label indicates a proposals which enhance the standard or add additional features. Type labels display the intended field of the issue. Type labels are static and never change. (Old label name: Feature)

  • Issues
  ·
  • Merge requests

  Simulation
• isType:RepositoryInfrastructure
  This label indicates that the issue deals with a topic related to the repository infrastructure such as CI, builds, document toolchain or similar. Type labels display the intended field of the issue. Type labels are static and never change. (Old label name: Build)

  • Issues
  ·
  • Merge requests

  Simulation
• requires:CCBReview
  This label indicates that the concept of this issue and a matching merge request is ready for review by the CCB. Requirement labels indicate an action to be fulfilled by the involved parties. Requirement labels can change. Old Requirement labels shall be removed. (Old label name: NeedsCCBReview)

  • Issues
  ·
  • Merge requests

  Simulation
• requires:ConceptualWork
  This label indicates that this issue needs conceptual work by an expert or an expert group. Requirement labels indicate an action to be fulfilled by the involved parties. Requirement labels can change. Old Requirement labels shall be removed. (Old label name: needsClarification)

  • Issues
  ·
  • Merge requests

  Simulation
• requires:DocumentationWork
  This label indicates that this issue needs a change of the documentation which has to be implemented by a project member. Requirement labels indicate an action to be fulfilled by the involved parties. Requirement labels can change. Old Requirement labels shall be removed. (Old label name: Documentation (Editorial Changes))

  • Issues
  ·
  • Merge requests

  Simulation
• requires:Merge
  This label indicates that this issue or a merge request is approved by the CCB and should be merged by a project member with the necessary rights. Requirement labels indicate an action to be fulfilled by the involved parties. Requirement labels can change. Old Requirement labels shall be removed. (Old label name: ReadyToMerge)

  • Issues
  ·
  • Merge requests

  Simulation
• requires:MergeRequest
  This tag indicates that this topic has a concise concept that is ready to be implemented in a merge request (either in the form of technical documentation, writing code, or model development). Requirement labels indicate an action to be fulfilled by the involved parties. Requirement labels can change. Old Requirement labels shall be removed. (Old label name: Implementation)

  • Issues
  ·
  • Merge requests

  Simulation