Skip to content

🐛 tracker: mention-tier links bind uncovered sibling issues ('#N remain') and closed superseded PRs into PR rows #14667

Closed

Description

@clubanderson

Symptom

The activity tracker's soft-link tiers (Refs #N, (#N, part 1) titles, first-paragraph mentions — #13544) bind a PR to issues it explicitly does not cover, and to closed PRs, producing wrong rows:

  1. Sibling-issue mention rendered as a covered issue. ✨ feat(agent,dashboard): repeat-failure row note, check states, no-data safeguard and coverage table #14623 body: "Closes [scanner] repeat-failure: dashboard row note, check states, no-data safeguard, coverage table and docs #14558 / Part of 🌱 [v6] agents: notice an agent repeating the same failing command (every backend, monitor-only) #14550 (tracker; [scanner] repeat-failure: backend-specific routes (copilot, omp, openhands, muse, agy, aider) and real-run evidence #14559 backend-specific routes remain)". The tracker renders three rows for ✨ feat(agent,dashboard): repeat-failure row note, check states, no-data safeguard and coverage table #14623: [scanner] repeat-failure: dashboard row note, check states, no-data safeguard, coverage table and docs #14558 (closing — correct), 🌱 [v6] agents: notice an agent repeating the same failing command (every backend, monitor-only) #14550 (refs + tracker 3/5 — correct, it is the tracker with 3/5 sub-issues done), and [scanner] repeat-failure: backend-specific routes (copilot, omp, openhands, muse, agy, aider) and real-run evidence #14559 — an issue at stage/010-actionable with no PR, shown as a PR row at "Fixing" + needs rebase. The PR text says the opposite: [scanner] repeat-failure: backend-specific routes (copilot, omp, openhands, muse, agy, aider) and real-run evidence #14559 is the remaining, uncovered work. ([scanner] repeat-failure: backend-specific routes (copilot, omp, openhands, muse, agy, aider) and real-run evidence #14559 was briefly 020-claimed 17:29–17:33Z then went back to 010 at 17:45Z; the tracker still shows it under ✨ feat(agent,dashboard): repeat-failure row note, check states, no-data safeguard and coverage table #14623.)

  2. Closed/superseded PR rendered as "(title unavailable)" issue. ✨ feature(crux): export OTel spans and kick metrics over OTLP when configured #14618 body: "Supersedes ✨ feature(crux): export OTel spans and kick metrics over OTLP when configured #14592 …". ✨ feature(crux): export OTel spans and kick metrics over OTLP when configured #14592 is Karibhou's closed PR (adoption mode=supersede superseded_by=14618). The tracker shows row "✨ feature(crux): export OTel spans and kick metrics over OTLP when configured #14592 (title unavailable) → PR ✨ feature(crux): export OTel spans and kick metrics over OTLP when configured #14618". stageTrackerPruneSoftLinks drops soft links to PRs only when the target is in the open-PR map; a closed PR is not, so it falls through as an issue and the issue title lookup fails. 🐛 fix(dashboard): enrich soft-linked stage-tracker issues with title and state #14630 (title/state enrichment, 🐛 dashboard: refs-linked issues show "(title unavailable)" — no title/state enrichment for soft links (not covered by #14579) #14606) would at best paint a PR title into the issue slot; it does not make the row correct.

Expected

  • Mention-tier links must not bind when the surrounding text negates coverage ("remain", "remains", "out of scope", "follow-up", "not in this PR", "see #N for …") or when the number appears inside a parenthetical after a tracker reference. At minimum, a mention of an issue whose own stage is 010-actionable/015-triage-needed with no claim should not be drawn as covered by the PR.
  • Supersedes #N / Replaces #N / any reference whose target is a PR (open or closed) must be excluded from the issue slot (resolve the number's type via the snapshot or the issues API pull_request field); if useful, draw it as a supersedes #N chip on the PR row instead.
  • One PR covering several issues: render once, grouped (issue chips in one row), rather than one full row per issue — three identical ✨ feat(agent,dashboard): repeat-failure row note, check states, no-data safeguard and coverage table #14623 rows with the same stage/pills read as three stalled PRs.

Evidence from 2026-10-27 18:18Z screenshot of hosted-available-oke-11-placeholder-r05x. Distinct from #14606 (missing title enrichment) — these rows should not exist at all.

Activity

  1. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Oct 27, 2026
  2. 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

    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