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

Labels

  • MRLogging
    Merge request label for indicating work related to internal audit, logging, reporting improvement
  • MRNew Feature
    Merge request label for indicating new feature change
  • MRNotice update
    Merge request label for indicating notice update
  • MRRefactor
    Merge request label for indicating work related to code clean ups/refactoring/optimization
  • MRRevert
    Merge request label for indicating reverting change
  • MRTesting
    This MR relates to changes for unit, integration, etc. testing
  • Pipeline Failure
    MR pending failures and requires investigation
  • PriorityCritical
    Catastrophic issue identified - Severe impact, contain breaking workflow/data loss, zero-day/critical security vulnerabilities No workaround and should be fixed as an immediate priority Need to be released as a patch during regular milestone cycle as soon as a fix is available
  • PriorityHigh
    Major issue identified - High impact, might contain breaking workflow/data loss, critical/high security vulnerabilities There is a workaround that exists but should be fixed as the next priority Might need to be released as a patch during regular milestone cycle/N+1 milestone release
  • PriorityLow
    Minor issue identified - Low impact, no breaking workflow/any workflow, medium/low security vulnerabilities There is a workaround that exists Can be released in N+1 or more milestone releases
  • PriorityMedium
    Serious issue identified - Medium impact, no breaking workflow/no data loss, high/medium security vulnerabilities There is a workaround that exists and should be fixed after high priority Can be released in N+1 milestone release
  • R3 - Deployment & Ops Support
  • R3 Development
  • R3-Discovery & Evaluation
    Any issues that need discovery / evaluation to get team to starting point, will be part of this title
  • R3 - Global Deployment
  • Release Notes Candidate
    Ideal for inclusion in upcoming milestone release notes
  • SeverityCritical
    This defect indicates complete shut-down of the process, nothing can proceed further and constitutes a breaking defect
  • SeverityLow
    This defect is low impact, no breaking workflow/any workflow, medium/low security vulnerabilities There is a workaround that exists
  • SeverityMajor
    This defects is a major issue but certain parts of the system remain functional.
  • SeverityMedium
    This defect has medium impact, no breaking workflow/no data loss, high/medium security vulnerabilities There is a workaround that exists and should be fixed after high priority