Skip to content

dashboard: tracker rows should order attention-first within each column #14686

Closed

Description

@clubanderson

Problem

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:

  1. Needs attention — stageTrackerNeedsAttention(row) is true (shown modifiers or a human-gated stage; deferred_modifiers from 🌱 dashboard: defer merge-gate pills until the PR reaches the gate #14651 never promote a row).
  2. Normal rows.
  3. Sunk — hold (incl. do-not-merge/*), draft, and closed-issue-anchored PRs (closed_issue, 🐛 dashboard: anchor tracker rows on the open PR when the issue has closed #14657) go last.

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.

Activity

  1. added
    kind/featureCategorizes issue or PR as related to a new feature.
    dashboardDashboard UI and API issues
    on Oct 27, 2026
  2. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Oct 27, 2026
  3. added a commit that references this issue on Oct 27, 2026
    deee564
  4. github-actions commented on Oct 27, 2026

    @github-actions
    Contributor

    @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.

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

    dashboardDashboard UI and API issueshelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/featureCategorizes issue or PR as related to a new feature.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions