Skip to content

Prioritized labels

Drag to reorder prioritized labels and change their relative priority.

Other labels

  • content
    FCHH Software
    decide on content question
  • develop
    FCHH Software / fabchain
  • discuss
    FCHH Software / fabchain
  • energy
    FCHH Software / fabchain
    related matter
  • food
    FCHH Software / fabchain
    related matter
  • metal
    FCHH Software / fabchain
    related matter
  • plan
    FCHH Software / fabchain
  • plastic
    FCHH Software / fabchain
    related matter
  • textiles
    FCHH Software / fabchain
    related matter
  • wiki
    FCHH Software
  • wood
    FCHH Software / fabchain
    related matter
  • ~priority::1
    FCHH Software
    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
  • ~priority::2
    FCHH Software
    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
  • ~priority::3
    FCHH Software
    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
  • ~priority::4
    FCHH Software
    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
  • ~severity::1
    FCHH Software
    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
  • ~severity::2
    FCHH Software
    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
  • ~severity::3
    FCHH Software
    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
  • ~severity::4
    FCHH Software
    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