Prioritized labels 0
Drag to reorder prioritized labels and change their relative priority.
Labels 2,864
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
priority1
GitLab.org
We will address this as soon as possible regardless of limit on our team capacity. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority
priority2
GitLab.org
We will address this soon and will provide capacity from our team for it in the next few releases. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority
priority3
GitLab.org
We want to address this but may have other higher priority items. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority
priority4
GitLab.org
We don't have visibility when this will be addressed. See https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#priority