Skip to content

Attention Required tab: group plans into Informational vs. Needs-Attention sections in priority order #16063

Description

@MrJustinB

Summary

On the Attention Required tab (PM View — Release Plan Health), reorganize the eight release-plan groups into two clearly labeled sections so that informational groups are visually separated from groups that require PM action, and the action groups are sorted in priority order.

Problem

The Attention Required tab currently lists eight groups in an order that does not reflect priority or whether action is actually needed:

  1. Ready to Complete Private Preview Release Plans
  2. Missing Namespace Approval
  3. Approaching SDK Release Target (This & Next Month)
  4. Past Due Release Plans
  5. Stale Release Plans (No activity for 3+ months)
  6. Release Plans Without SDK for All Languages
  7. Partially Released
  8. Recently Finished (Last 2 Months)

Two of these groups (Approaching SDK Release Target, Recently Finished) are informational and do not require immediate PM action, yet they are interleaved with the groups that do. The action-needed groups are also not ordered by urgency, making it harder to know what to work on first.

Proposed solution

Group the eight sections into two labeled sections, top to bottom:

Section 1 — Informational (no immediate action)

  1. Recently Finished (Last 2 Months)
  2. Approaching SDK Release Target (This & Next Month)

Section 2 — Needs Attention (priority order)

  1. Ready to Complete Private Preview Release Plans
  2. Past Due Release Plans
  3. Stale Release Plans (No activity for 3+ months)
  4. Release Plans Without SDK for All Languages
  5. Partially Released
  6. Missing Namespace Approval

Acceptance criteria

  • The eight existing groups are rendered under two visually distinct section headers: an "Informational" (or similar) section and a "Needs Attention" (or similar) section.
  • Within each section, groups appear in the exact order listed above.
  • Each group retains its existing collapse/expand behavior and item counts.
  • No release-plan groups are dropped or duplicated; all eight remain present.
  • Ordering is stable regardless of how many items each group contains (including empty groups showing "(0)").

Notes

  • Current state for reference: see PM View — Release Plan Health on the Attention Required tab.
  • Section labels are a suggestion; final wording is at implementer discretion as long as the two-section grouping and intra-section ordering are preserved.

Metadata

Metadata

Labels

API Spec & SDK release processAPI Spec & SDK library creation, generation, and publishing processes.

Fields

No fields configured for Feature.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions