Labels

Indicates that Data Team should perform a impact check on the MR

Indicates that there is a impact on Data Warehouse

Indicates that this MR is not impacting Data Warehouse

Provide the data team with awareness of an issue that may affect data (reporting, compliance, process)

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

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)