Other labels
AIF-Priority3
GitLab.org
A label to denote the priority of issues related to the AI Framework team, see https://handbook.gitlab.com/handbook/engineering/development/data-science/ai-powered/ai-framework/
AIF-Priority2
GitLab.org
A label to denote the priority of issues related to the AI Framework team, see https://handbook.gitlab.com/handbook/engineering/development/data-science/ai-powered/ai-framework/
AIF-Priority1
GitLab.org
A label to denote the priority of issues related to the AI Framework team, see https://handbook.gitlab.com/handbook/engineering/development/data-science/ai-powered/ai-framework/
SAST::RulesetP1
GitLab.org
Denotes denotes a high priority rule, likely coming from a customer escalation or reported to us as desirable by potential customers.
SAST::RulesetP2
GitLab.org
Denotes denotes a moderate priority rule, one we should research and implement in the near term.
SAST::RulesetP3
GitLab.org
Denotes denotes a medium priority rule, one we should look to implement in the mid term.
SAST::RulesetP4
GitLab.org
Denotes denotes a low priority rule, one we could look to implement in the long term or after its reprioritized.
groupux paper cuts
GitLab.org
Used by the UX Paper Cuts team for **planning only**. If you have a suggestion for the team, please add the ~UX Paper Cuts label!
Category:Rich Text Editor
GitLab.org
Category Label for Rich Text Editor (also known as Content Editor). This Category falls under Plan Stage, Knowledge Group.
priority4
GitLab.org
We don't have visibility when this will be addressed. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority
priority3
GitLab.org
We want to address this but may have other higher priority items. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority
priority2
GitLab.org
We will address this soon and will provide capacity from our team for it in the next few releases. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority
priority1
GitLab.org
We will address this as soon as possible regardless of limit on our team capacity. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority
severity4
GitLab.org
Low - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#severity
severity3
GitLab.org
Major - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#severity
severity2
GitLab.org
Critical - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#severity
severity1
GitLab.org
Blocker - applies to bugs and bug categories of availability, performance, security and ux. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#severity
groupimport and integrate
GitLab.org
Issues, MRs and Epics belong to group::import and integrate https://handbook.gitlab.com/handbook/engineering/development/dev/manage/import-and-integrate/
resulted from merging group::integrations and group::import | PM: @m_frankiewicz
Prioritized