Labels

Engineering Allocation Requested by Quality https://about.gitlab.com/handbook/engineering/engineering-allocation

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

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

Engineering Allocation requested by UX https://about.gitlab.com/handbook/engineering/engineering-allocation

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

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

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

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