Labels

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/

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/

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/

AppSec top priority work that must be completed for the end of the planned milestone.

AppSec work priority that is important and is prioritized as soon as all ~"AppSecPriority::1" work is completed. ~"AppSecPriority::2" work will become ~"AppSecPriority::1"` on the next milestone.

AppSec work priority that is less important and is prioritized as soon as all ~"AppSecPriority::2" work is completed. ~"AppSecPriority::3" will be evaluated during Milestones Planning Sessions and may become ~"AppSecPriority::2" for the next milestone.

Priority Score based on Customer Issues Prioritization Framework (https://about.gitlab.com/handbook/product/product-processes/customer-issues-prioritization-framework/#priority-score); From highest to lowest priority: CISP::1, CISP::2, CISP::3, CISP::4. These priorities represent separate buckets for features and bugs. And these are again separated by group. Currently, this label is only applied to ~type::bug and ~"group:source code"

Priority Score based on Customer Issues Prioritization Framework (https://about.gitlab.com/handbook/product/product-processes/customer-issues-prioritization-framework/#priority-score); From highest to lowest priority: CISP::1, CISP::2, CISP::3, CISP::4. These priorities represent separate buckets for features and bugs. And these are again separated by group. Currently, this label is only applied to ~type::bug and ~"group:source code"

Priority Score based on Customer Issues Prioritization Framework (https://about.gitlab.com/handbook/product/product-processes/customer-issues-prioritization-framework/#priority-score); From highest to lowest priority: CISP::1, CISP::2, CISP::3, CISP::4. These priorities represent separate buckets for features and bugs. And these are again separated by group. Currently, this label is only applied to ~type::bug and ~"group:source code"

Priority Score based on Customer Issues Prioritization Framework (https://about.gitlab.com/handbook/product/product-processes/customer-issues-prioritization-framework/#priority-score); From highest to lowest priority: CISP::1, CISP::2, CISP::3, CISP::4. These priorities represent separate buckets for features and bugs. And these are again separated by group. Currently, this label is only applied to ~type::bug and ~"group:source code"

customer satisfaction priority

customer satisfaction priority

customer satisfaction priority

Issue for @courtmeddaugh to work on that is not a current priority.

Used to denote an issue which will impact Commercial customers. Typically added if repeatedly seen by the Commercial Sales team.

The sole purpose of this label is to communicate common bugs that the Provision Team have identified. This could probably be replaced by a more complex search using a combination of type::bug, priority::1, etc. when &291 is completed

This label is applied to Epics and Issues that must be prioritized above all other work for the Feb 10th launch, including the highest‑priority parallel work that must continue in support of DAP launch strategy