Labels

(Large) Requires effort in validation through replication or research. Typically, more than a paragraph, less than a page.

(Very Large) Solution may not be straightforward or known. Significant investigation or expert knowledge required. Typically revising up to a full page, or sections of multiple pages.

For documentation-labeled items, use when content is added or updated for a new or changed feature, including MRs where the technical writer reviews a developer's work. Generally used with `feature` label.

For documentation-labeled items, use for content changes that resolve identified issues, including inaccurate or unclear content, typos, style problems, outdated screenshots, or bad URLs.

For documentation-labeled items, use for content changes not related to newly introduced features, fixes, or non-content structural items.

For documentation-labeled items, use when changes don't affect visitor readable, rendered content. Includes metadata, markdown code (incl. tiers or admonitions), and redirects.

Epics, issues, and merge requests related to Algolia search for the Docs site

Epics, issues, and merge requests related to Google search for the Docs site

Epics, issues, and merge requests related to lunr.js search for the Docs site

Epics, issues, and merge requests related to product documentation.

Followup tasks which are scheduled, but blocked and pending until a future date. Intended to be used issues related to GraphQL deprecations, field rename DB migrations, etc, which cannot be completed until a given number of releases have passed.

[Phase 1] Incorporate Duo Nano into Premium/Ultimate plans without seat assignment

Developer Experience contributor-tooling-related issues

Developer Experience infrastructure-related issues

Developer Experience meta issues

Developer Experience metrics-related issues