Labels

This indicates an issue or merge request related to broken JiHu pipeline, including JH validation pipeline

Contribution from the JiHu team

This indicates an issue or merge request can impact JiHu

Issues related to GitLab for Jira Cloud app, docs:https://docs.gitlab.com/ee/integration/jira/connect-app.html, which allows to use the Jira development panel. Used to be called Jira Connect App.

Issues related to the installation and configuration of Jira integrations

Issues related to the Jira issue integration, docs: https://docs.gitlab.com/ee/integration/jira/configure.html.

All issues and MRs related to framing Jobs to be Done (JTBD) - https://about.gitlab.com/handbook/engineering/ux/jobs-to-be-done/

Issues discovered during GitLab.com K8s migration project gitlab-com/gl-infra&112, requiring more work. Owner: team::Delivery

Kubernetes Agent Server (KAS) related. Owner group::environments

Issues to highlight in the monthly Kickoff call (https://about.gitlab.com/handbook/engineering/workflow/#kickoff).

Items of top priority as indicated by Knowledge Group PM.

Priority 1 Issues for Knowledge Group in Plan Stage.

Priority 2 Issues for Knowledge Group in Plan Stage.

Priority 3 Issues for Knowledge Group in Plan Stage.

This label should be used by any team member who requires the Localization team attention/review/feedback on an issue

Localization issue, MR, or epic that impacts the workflows of the Technical Writing team or the docs.gitlab.com site and infrastructure.

Label to be used when an edit to a localized file has been made outside of the localization workflow.

Label to be used when an edit to a localized file on GitLab is now accounted for in the localization workflow.

This MR was created by a Leading Organization