Labels

Cohort A — Subset of Inactive Free Users. Up to 5,000 organizations. Purpose: Establish Protocells in real production use and refine the migration process. Eligibility: Inactive root namespaces · Free plan · Private only. Exit criteria impact: Tiny impact on database size.

Cohort B — Active Opt-in Beta. Up to 1,000 organizations. Purpose: Gain experience with real daily active users. Eligibility: Opt-in / guided · Active root namespaces · Free or paid · Private only. Exit criteria impact: Tiny impact on WAL, LWLocks and database size.

Cohort C — Top 1000 Opt-in. Up to 300 organizations. Purpose: Relieve the legacy cell. Eligibility: Opt-in / guided · Top 1,000 root namespaces by database time · Private only · Prerequisite: Feature parity. Exit criteria impact: At least 20% decrease in WAL saturation and database size.

Applied once community bonus points have been awarded

If you solve this issue, you'll be assigned a community bonus of 100 points

If you solve this issue, you'll be assigned a community bonus of 200 points

If you solve this issue, you'll be assigned a community bonus of 300 points

If you solve this issue, you'll be assigned a community bonus of 500 points

Label used to track work related to improving data integrity across gitlab (as it pertains to project Compass). https://about.gitlab.com/direction/product-intelligence/#resolve-data-integrity-concerns

Issues that are related to competing with another tool or solution identified during Competitive Roadmap Reviews

Features in monday.com

An issue which has been validated, broken down, planned/designed, developed, deployed, but not verified in production. 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, broken down, planned/designed, developed, deployed, and verified in production. 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

Issue with high technical complexity. Complexity does not describe the time it will likely require to address the issue, but rather the familiarity required to address it. This label is only intended as a guideline to hint to individuals how involved the issue will likely be.

Issue with low technical complexity. Complexity does not describe the time it will likely require to address the issue, but rather the familiarity required to address it. This label is only intended as a guideline to hint to individuals how involved the issue will likely be.

Issue with medium technical complexity. Complexity does not describe the time it will likely require to address the issue, but rather the familiarity required to address it. This label is only intended as a guideline to hint to individuals how involved the issue will likely be.

Pajamas Design System: Accordion component

Pajamas Design System: Alert component

Pajamas Design System: Avatar component