Skip to content

πŸ› dashboard: refs-linked issues show "(title unavailable)" β€” no title/state enrichment for soft links (not covered by #14579)Β #14606

Closed

Description

@clubanderson

Symptom

Stage-tracker PR rows whose only linked issue comes from a soft refs reference render the issue as "(title unavailable)", even when the issue exists and is closed.

Instance hosted-available-oke-11-placeholder-r05x, /api/stage-tracker at 16:52Z:

14597  linked_issues: [{"number":14576,"url":"https://github.com/hive/issues/14576","via":"refs"}]
14590  linked_issues: [{"number":14577,"url":"https://github.com/hive/issues/14577","via":"refs"}]

Both #14576 and #14577 are real, CLOSED issues in hivecommons/hive. The payload has no title and no state for them, so stageTrackerPRIssueSlot falls through to STAGE_TRACKER_UNTITLED_ISSUE (it cannot even pick the "closed" placeholder because state is empty).

Not covered by #14579

#14579 (stageTrackerSameRepo, merged 15:17Z, not yet deployed here) fixes the dropped titled closing link and the short-name URL. Its own test fixture shows the refs case is left untitled by design:

{Number: 14560, URL: "https://github.com/hivecommons/hive/issues/14560", Via: github.PRLinkViaRefs},

So after #14579 lands these rows will get the right URL but still read "(title unavailable)".

Expected

Soft-linked (refs / title / mention) issues in the same repo should be enriched with title + state the same way closing links are (one issues GET per distinct number, cached with the tracker TTL), or the frontend should render the number + "refs" chip without the alarming placeholder when the server only knows the number.

Activity

  1. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Oct 27, 2026
  2. hivecommons-hive commented on Oct 27, 2026

    @hivecommons-hive
    Contributor

    πŸ”’ Claimed by agent scanner (agent on hive hosted-available-oke-11-placeholder-r05x). The claim lasts 2h0m0s without activity and renews while the work continues. Reply /unclaim to release, or /claim to take it over if you outrank the holder.

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