Other labels
pipeline:run-as-if-foss
GitLab.org
Indicates that associated merge request pipeline jobs would run in the context of the `gitlab-org/gitlab-foss` project
pipeline:run-as-if-jh
GitLab.org
Indicates that associated merge request pipeline will trigger a cross project downstream pipeline in GitLab JH validation project. See https://docs.gitlab.com/ee/development/pipelines/#as-if-jh-cross-project-downstream-pipeline Can be disabled by setting $CI_AS_IF_JH_ENABLED to `false`
pipeline:run-clusterwide-db
GitLab.org
Setups databases with a new connection `main_clusterwide`, but pointing to the same database as `main`, and run RSpec jobs with this DB configuration.
pipeline:run-praefect-with-db
GitLab.org
Run tests with Praefect using a PostgreSQL database instead of an in-memory election strategy
pipeline:run-review-app
GitLab.org
Indicates that associated merge request pipelines will be forced to deploy a review app regardless of the changes
pipeline:run-single-db
GitLab.org
Indicates that associated merge request pipelines will be run jobs with a single database
pipeline:skip-undercoverage
GitLab.org
Indicates that the undercoverage job for the merge request will be allowed to fail
pipeline:update-cache
GitLab.org
Indicates that associated merge request pipelines will be run jobs to force caches to be updated
plantriage
GitLab.org
An issue that is not assigned an epic, milestone, or contains not enough information. It requires more triaging to decide its fate.
planning priority
GitLab.org
Issues which are particularly important to be released in the specified milestone. This should only be set by the responsible PM.
planningrefinement
GitLab.org
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
planningto-do
GitLab.org
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
platform-specific
GitLab.org
Outlier that relates to a single distribution, platform, or architecture (eg Debian/AWS/ARM/)
platform-to-create
GitLab.org
Issues migrated from Platform label to Create label Ref: gitlab-org/quality/triage-ops#59
popular proposal
GitLab.org
Feature proposals deemed popular by our issue triage policies (https://gitlab.com/gitlab-org/triage) will have this label applied
portal integration
GitLab.org
for issues relating to the customer portal integrating with another ent app
potential proposal
GitLab.org
Label added by triage tools to mark interesting feature proposals for consideration
Prioritized