IT Engineering. This is for issues that are higher priority than BAU and OKR work are are measured to understand how much time is spent on distractions.

IT Engineering. This is for research or side projects that don't have conventional metrics.

IT Engineering. This is used for code related to for features, workflows included in OKRs or BAU.

IT Engineering. This is used for code related to bugs and unplanned features.

IT Engineering. This is used for docs related to features, workflows, bugs or handbook updates.

Cross-functional, collaborative actions derived from CAB activities

Events happening during the KubeCon/CloudNativeCon events

GitLab, like most large applications, enforces limits within certain features. The absences of limits can impact security, performance, and availability. For this reason issues related to limits are considered as another category of ~"type::bug". https://about.gitlab.com/handbook/engineering/quality/issue-triage/#limit-related-bugs

AMER SDR awareness is needed for potential questions in regards to events

APAC SDR awareness is needed for potential questions in regards to events

EMEA SDR awareness is needed for potential questions in regards to events

No direct action needed from Business Technology but awareness for potential questions

Indicates content that requires MPM.

No direct MktgOps action item, but Ops awareness is needed for potential questions

work that directly relate to an OKR

work that does not directly relate to an OKR but has a large impact on the field team

work that does not directly relate to an OKR and has a low to medium impact on the field

IT Engineering. Applied to all data migration related issues.

Current OKR of the Marketing Ops team (Fy22 Q4)