Labels

The work type isn’t entirely clear yet, but we don’t want to block progress for now.

Functionality required by GitLab Product Security teams.

Indicates that an issue represents a specific feature or piece of functionality required to eventually deprecate a custom tool used by Product Security teams.

Work done as part of the effort to integrate functionality from custom in-house tooling into a GitLab product.

Product Security Engineering Priority Level 1. This issue requires immediate attention and should be worked on as soon as possible. Typically, it is added to the next milestone or addressed during the current one if a team member has extra capacity

Product Security Engineering Priority Level 2. This issue is essential but can wait for a few milestones.

Product Security Engineering Priority 3. This issue is a nice-to-have, but we do not commit to a specific timeline.

Used by Product Security Department Sub Teams for their workflow labels for completed requests.

Used by Product Security Department Sub Teams for their workflow labels for new requests.

Used by Product Security Department Sub Teams for their workflow labels for ongoing requests.

Used by Product Security Department Sub Teams for their workflow labels for planned requests.

Tag for Product Leadership initiatives

Applies to issues concerning optimization of product management frameworks, product development flow, product strategy and planning.

For work being performed by the Product Security Engineering Team: https://handbook.gitlab.com/handbook/security/product-security/product-security-engineering/

https://gitlab.com/groups/gitlab-org/-/epics/10336