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
dashboard: tracker rows should order attention-first within each column #14686
The Activity tracker orders rows within a column by stage_since (oldest first) → repo → number. Nothing floats the rows a person must act on now (085 needs-decision, 090 ready-for-human-merge, 071/072 returned to a human author, stalled, unauthorized on held runs, needs rebase on a human-authored PR) and nothing sinks the rows nobody should act on (hold / do-not-merge/*, draft, PRs anchored on a closed issue). In a busy column the human-gated row can sit below a dozen hive-driven rows that merely entered the stage earlier.
The server pre-sorts the payload stage desc → oldest StageSince → repo → number (stage_tracker.go), so API consumers (chat /prs, hub) see the same flat order.
Proposal (owner approved)
Within each column / stage band, for the furthest and waiting sorts, order rows in three tiers before the existing keys:
Within a tier keep stage_since oldest → repo → number. The ↓/↑ direction toggle flips only the age/repo/number keys, never the tier order (attention stays on top in both directions); the button tooltip says so. newest and number sorts are untouched. Sub-rows under an issue tier the same way; Group=Repo still groups after sorting.
Mirror the tier in the server pre-sort so API consumers see the same order; one tier function on each side (stageTrackerAttentionTier in Go and JS) with a Go test and a node fixture test asserting tier order and that desc/asc keep tiers.
No new chrome: the existing pills already explain why a row is on top.
@clubanderson this issue was closed by @hivecommons-hive[bot] as completed.
If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.
If you are still seeing the problem, comment /reopen and it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.
Activity
✨ dashboard: order tracker rows attention-first within each column (#…
github-actions commentedon Oct 27, 2026
@clubanderson this issue was closed by @hivecommons-hive[bot] as completed.
If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.
If you are still seeing the problem, comment
/reopenand it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.