Run tests with Praefect using a PostgreSQL database instead of an in-memory election strategy

Indicates that associated merge request pipelines will be forced to deploy a review app regardless of the changes

Indicates that associated merge request pipelines will be run jobs with a single database

Indicates that the undercoverage job for the merge request will be allowed to fail

This is an automatically-applied label when the latest pipeline on a merged MR was creating too long ago at the time of merging.

Indicates that associated merge request pipelines will be run jobs to force caches to be updated

An issue that is not assigned an epic, milestone, or contains not enough information. It requires more triaging to decide its fate.

Issues which are particularly important to be released in the specified milestone. This should only be set by the responsible PM.

An issue which has been validated and breakdown started, but requires further refinement before development can begin. This label is being used as part of an experiment and should not be manually added/removed. See gitlab-org/developer-relations/contributor-success/team-task#382

An issue which has been validated and ready for planning/design/development. This label is being used as part of an experiment and should not be manually added/removed. See gitlab-org/developer-relations/contributor-success/team-task#382

Outlier that relates to a single distribution, platform, or architecture (eg Debian/AWS/ARM/)

Issues migrated from Platform label to Create label Ref: gitlab-org/quality/triage-ops#59

Feature proposals deemed popular by our issue triage policies (https://gitlab.com/gitlab-org/triage) will have this label applied

for issues relating to the customer portal integrating with another ent app

Label added by triage tools to mark interesting feature proposals for consideration

Issues that we anticipate yielding higher predictability (vs. velocity).