Labels

Used to denote the relative customer priority when including a link to SFDC or ZenDesk on an issue or epic. 1 is the lowest and 10 is the highest. See https://about.gitlab.com/handbook/product/how-to-engage/#feedback-template for more info.

Used to denote the relative customer priority when including a link to SFDC or ZenDesk on an issue or epic. 1 is the lowest and 10 is the highest. See https://about.gitlab.com/handbook/product/how-to-engage/#feedback-template for more info.

Input from customer success team

Features and bugs reported by large enterprise customers. This label is in use by the product org, please post in #product Slack channel if you have questions.

Issues for collaboration with customers specifically for issues under https://gitlab.com/gitlab-com/account-management

For Support: Use to denote that an issue or merge request was opened as an action item from a Support ticket retrospective.

Part of the Customer Happy Paths Project

Work associated with a dark mode for the user interface of GitLab

Issues that relate to dashboard customization. Read more at https://about.gitlab.com/direction/monitor/platform-insights/custom-dashboards-foundation/

Issues that relate to dashboard data exploration. Read more at https://about.gitlab.com/direction/monitor/platform-insights/custom-dashboards-foundation/

Issues that relate to dashboard layout framework. Read more at https://about.gitlab.com/direction/monitor/platform-insights/custom-dashboards-foundation/

Issues that relate to dashboard navigation and data hierarchy. Read more at https://about.gitlab.com/direction/monitor/platform-insights/custom-dashboards-foundation/

This check includes callback payloads

This check requires a DAST engine to define it's own implementation according to the specification

This check includes payloads that match a response

This check includes a passive check

This check includes a payload which does timing based analysis

A DAST CWE check is ready for implemention

A DAST CWE check requires research