Skip to content

Activity Monitor: issues sharing one PR are scattered across the list #17332

Closed

Description

@clubanderson

What

On the live Activity Monitor, issue #17292 (primary; PR #17308 "also closes #17302") sits at the top, an unrelated row (#17329) sits between, and #17302 (the secondary issue the same PR closes) is third. #17325 made the secondary ride the PR's lane (the ↳ #17308 · under #17292 chip), but the rows themselves are still scattered — they are one flow and should read as one.

Expected

Shared-PR grouping:

  1. Ordering — secondary issues closed by the same PR always render immediately after their primary row, regardless of the lead sort; the group sorts by the primary. If the primary is filtered out the secondary stays standalone (as today).
  2. Visual — the secondary row is drawn as a child of the primary (indent + connector rail), consistent with the existing ↳ #PR · under #primary chip. Both rows render from the same PR snapshot — no separate stale copy.
  3. Fold — the primary's existing also closes #N pill gets a small caret that collapses/expands the secondary rows; default expanded; persisted in localStorage like the other tracker toggles.
  4. Tests for adjacency with an unrelated row between, fallback when the primary is filtered out, and same-snapshot rendering; one short paragraph in the Activity Monitor doc.

Follow-up to #17324 / #17325.

Activity

  1. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Nov 9, 2026
  2. added a commit that references this issue on Nov 9, 2026
    ba6e44c
  3. added a commit that references this issue on Nov 9, 2026
    a94ef95
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions