Engineering Allocation Work Produced by Security https://about.gitlab.com/handbook/engineering/engineering-allocation

Engineering Allocation Produced by Support https://about.gitlab.com/handbook/engineering/engineering-allocation

Engineering Allocation to be complete by UX https://about.gitlab.com/handbook/engineering/engineering-allocation

Used for identifying feedback and action around engagement surveys

Differentiate between Engineering and UX issues using relevant labels

Label to scope Engineering https://about.gitlab.com/handbook/engineering/#engineering-allocation

Issues pertaining to the Engineering Analytics team (https://about.gitlab.com/handbook/engineering/quality/engineering-analytics/)

Issues owned by the Engineering Productivity team. More at https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/

Indicates the issue was prioritized by Engineering. Used for metrics related to Product/Engineering prioritization split.

for portal to enterprise application ecosytem

identifies a gap in automation

This label is dedicated for issues closed in FY24'Q4

Issues and merge requests for GitLab Enterprise Edition

Work related to Enterprise Agile Portfolio and Project management, including SAFe

One of the 90 issues in Epic 6340. Using a label because some of these issues are already in other epics. Created by @djensen.

Combined with a group:: scoped label, this issue should improve the error budget availability score of the group