Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
portal integrationGitLab.comfor issues relating to the customer portal integrating with another ent app
-
priority1GitLab.comWe will address this as soon as possible regardless of limit on our team capacity. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
-
priority2GitLab.compriority 2 We will address this soon and will provide capacity from our team for it in the next few releases. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
-
priority3GitLab.comWe want to address this but may have other higher priority items. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
-
priority4GitLab.comWe don't have visibility when this will be addressed. See https://about.gitlab.com/handbook/engineering/quality/issue-triage/#priority
-
prodops:feedbackloopsGitLab.comrelates to prodops work focusing on Building Qualitative & Quantitative Feedback Loops
-
prodops:outcomesGitLab.comrepresents prod ops work supporting operationalizing outcome driven products
-
prodops:relatedGitLab.comThis label represents is used when an epic, issue or MR does not required direct contribution from Product Operations but required their awareness as it affects workflows, documentation, or is otherwise a dependency for Product Operations work.
-
prodops:releaseGitLab.comapplies to epics, issues or MRs that need to be highlighted on a product operations release page
-
product categoryGitLab.com
-
product intelligenceGitLab.comLabel for issues relating to GitLab's product usage data (usage ping) and version check (version.gitlab.com).
-
product intelligenceapprovedGitLab.comTelemetry changes are reviewed and ready to be approved by Telemetry Maintainer
-
product intelligencereview pendingGitLab.comProduct analytics changes require a review from product analytics review / maintainer.
Prioritized