Labels

Indicates that the issue is related to an ongoing DataSec investigation of legacy code and infrastructure.

This label indicates DataSec is doing some kind of miscellaneous work with this issue (i.e., consultative work at the request of another team that isn't spawning its own issue in our board).

Pertaining database engineering concepts, patterns, improvements, etc.

Improvements to database helpers, rubocop rules, and documentation

A label for all things related to the GitLab Debian repository

The Revenue Organization cannot sell the Dedicated SKU without this capability to the customer that was referenced.

The Revenue Organization is able to sell or keep the customer referenced in comment, but the customer is expecting committed delivery on this capability for Dedicated

The Revenue Organization cannot renew the Dedicated SKU without this capability with the customer that was referenced.

A follow-up issue for when we choose to deviate from the MVC, during implementation, in a way that harms the user experience. https://about.gitlab.com/handbook/engineering/workflow/#deferred-ux

Issues scheduled for the current milestone.

https://handbook.gitlab.com/handbook/security/security-engineering/product-security-engineering/

Create and update issue and MR templates in `.gitlab/*` (dev guidelines)

Design help needed for this issue

Use this label when you want to mark the priority of a design issue as the top priority (i.e. do this first as the top priority 1) where you're expecting to deliver it at a 100% by the defined due date.

Use this label when you want to mark the priority of a design issue as the second most important priority (i.e. do this second as the next priority 2) where you're expecting to deliver it at 80% by the defined due date.

Use this label when you want to mark the priority of a design issue as the third-highest priority (i.e. do this third as the medium priority 3) where you're expecting to deliver it at 60% by the defined due date.