Skip to content
GitLab

Prioritized Labels

Drag to reorder prioritized labels and change their relative priority.

Other Labels

  • textiles
    related matter
    FCHH Software / fabcity-interfacer-ui
  • wiki
    FCHH Software
  • wood
    related matter
    FCHH Software / fabcity-interfacer-ui
  • ~priority::1
    The priority label is used to indicate the importance and guide the scheduling of the issue. Priority labels are expected to be adjusted by the Product Manager based on the circumstances of the market, product direction, IACV impact, number of impacted users and capacity of the team. Compare: https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
    FCHH Software
  • ~priority::2
    The priority label is used to indicate the importance and guide the scheduling of the issue. Priority labels are expected to be adjusted by the Product Manager based on the circumstances of the market, product direction, IACV impact, number of impacted users and capacity of the team. Compare: https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
    FCHH Software
  • ~priority::3
    The priority label is used to indicate the importance and guide the scheduling of the issue. Priority labels are expected to be adjusted by the Product Manager based on the circumstances of the market, product direction, IACV impact, number of impacted users and capacity of the team. Compare: https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
    FCHH Software
  • ~priority::4
    The priority label is used to indicate the importance and guide the scheduling of the issue. Priority labels are expected to be adjusted by the Product Manager based on the circumstances of the market, product direction, IACV impact, number of impacted users and capacity of the team. Compare: https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
    FCHH Software
  • ~severity::1
    Severity labels help us determine urgency and clearly communicate the impact of a ~bug on users. There can be multiple categories of a ~bug. The presence of bug category labels ~availability, ~performance, ~security, and ~UX denotes to use the severity definition in that category. Compare: https://about.gitlab.com/handbook/engineering/quality/issue-triage/#examples-of-severity-levels
    FCHH Software
  • ~severity::2
    Severity labels help us determine urgency and clearly communicate the impact of a ~bug on users. There can be multiple categories of a ~bug. The presence of bug category labels ~availability, ~performance, ~security, and ~UX denotes to use the severity definition in that category. Compare: https://about.gitlab.com/handbook/engineering/quality/issue-triage/#examples-of-severity-levels
    FCHH Software
  • ~severity::3
    Severity labels help us determine urgency and clearly communicate the impact of a ~bug on users. There can be multiple categories of a ~bug. The presence of bug category labels ~availability, ~performance, ~security, and ~UX denotes to use the severity definition in that category. Compare: https://about.gitlab.com/handbook/engineering/quality/issue-triage/#examples-of-severity-levels
    FCHH Software
  • ~severity::4
    Severity labels help us determine urgency and clearly communicate the impact of a ~bug on users. There can be multiple categories of a ~bug. The presence of bug category labels ~availability, ~performance, ~security, and ~UX denotes to use the severity definition in that category. Compare: https://about.gitlab.com/handbook/engineering/quality/issue-triage/#examples-of-severity-levels
    FCHH Software