Decide whether to create the org Priority issue field

Abierto
#14,078 4 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@kyle-sexton ya está trabajando en esto.

Desde el 8/11/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

needs-triage priority: medium status: needs-decision

Decision

Create an org-level Priority issue field (single select) to replace the four priority: labels on issues, or keep the labels until issue fields leave public preview.

Context

  • GitHub ships Priority as a default issue field and recommends a single-select field for a preset list such as priority (Managing issue fields; Best practices for Projects, read 2026-11-08).
  • Issue fields are still documented as public preview.
  • Creating a field is an owner step in org settings, recorded in github-iac's expected-org-security drift record, as for Size, Complexity and Uncertainty (github-iac ADR 0016).
  • Option names follow the org rule for field options: lowercase kebab-case (owner decision Q18, 2026-11-08).

Done when

  • The owner creates the field (options critical, high, medium, low) and its ids are added to the github-iac drift record, or the owner chooses to keep the labels; either answer is recorded on this issue, which then closes.

Closing this issue unblocks #14074.

Lenguaje dominante
Shell
Estrellas
22
Forks
2
Merge medio
56 min
PR fusionados (30 d)
959

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de melodic-software/claude-code-plugins

Todos los issues de melodic-software/claude-code-plugins

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.