Skip to content

[FEATURE] Use Server Display Name in Job History tab #2126

Closed

Description

@ghauan

Which component(s) does this affect?

  • Lite
  • Darling
  • Documentation

Problem Statement

Both the filter dropdown and column header in the Job History tab in the viewer uses the real servername.

Proposed Solution

It would be preferable that it showed the Display Name the same as the other tabs do.

Use Case

Normally I don't remember all the actual servernames, rather I use the aliases we have for them.

Alternatives Considered

No response

Additional Context

No response

Activity

  1. erikdarlingdata commented on Aug 8, 2026

    @erikdarlingdata
    Owner

    Fixed on dev by #2128, both SKUs:

    • Darling Viewer: both Job History readers (job history + the Agent status header) resolve through the servers registry — COALESCE(display_name, raw name) — so the Server filter dropdown, the Server column, the per-column filter popup, and the CSV export all speak your aliases like every other tab, and the Agent roll-up sorts by them.
    • Lite got the same fix its own way (its display names live at the config layer, not in the store): the shell passes a server-id → alias snapshot into the tab on every refresh.

    A server no longer in your config keeps its raw collected name — job history is a durable record and rows can outlive their registration. It'll be in the current nightly (3.4.0-nightly.20260808) — thanks for the ask, this one was overdue.

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

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions