You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Activity Monitor: issues sharing one PR are scattered across the list #17332
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:
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).
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.
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.
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.
Activity
✨ Activity Monitor: shared-PR issues group under their primary row
✨ Activity Monitor: shared-PR issues group under their primary row (h…