Labels

Issues related to GitLab's (ab)use of its database

Any issues that group::database has scheduled and is working on. They are in the build phase of the product development flow.

Database changes are approved by Database Maintainer and are ready to be merged

Database changes require a review from Database Reviewer/Maintainer

Database changes are reviewed and ready to be approved by Database Maintainer

Label used to identify database table size above our new limitations. See https://docs.gitlab.com/ee/development/database/large_tables_limitations.html

Database-related issues and observations to be triaged by group::database (internal use in this group)

Issues that are in the validation phase of the product development flow. They are not yet ready for development (building).

For issues that are primarly related to dedicated-instances

Changes to default configuration values

This bug has had the default priority applied. Feel free to override. More info: gitlab-org/quality/triage-ops#29

This bug has had the default severity applied. Feel free to override. More info: gitlab-org/quality/triage-ops#29

This indicates issues that aim to enhance the overall security defense of the application and does not indicate a security vulnerability.

Issues and epics that contributes towards the Delivery Direction https://about.gitlab.com/direction/delivery/

Items that would make notable demonstration subject material

Demo Systems related issues that do not have direct responsibility or tasks.

Issues related to the Infrastructure Platforms department https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/

Issues about Dependency List feature (see &858). Formerly "bill of material"

issues and epics related to showing a dependency path to users