resolved 6c56541f-7e9a-4b1b-94d6-d29589811ebf
In addition to the timestamps in the UI, I want all the comments or items in the ticket history to say how long ago the comment was made, like at the main list of tickets, where it says how long ago a ticket was created or updated. I want to see how long before now a comment or ticket history item happened. Make this it's own subagent task, and make a deploy just for this, while any other work for other tickets is ongoing.
src/html.rs (ticket_detail): each entry in the <ul class="history"> list now renders the absolute RFC3339 timestamp followed by a muted parenthesized relative-age string. Same humanize_age(then, now) helper the ticket-list view already uses for ticket-level created/updated.
Pattern:
<span>2026-04-25T20:18:39Z <span class="sub">(3h ago)</span></span>
The absolute stamp is unchanged; the new annotation is small and uses the existing .sub style class for visual consistency with the rest of the page's muted text.
89a64c0 feat(ui): show relative age next to ticket history timestampsmain: 868fb75 Merge branch 'chore/ticket-history-age'Pushed to gitlab/main and deployed via bash k8s/deploy.sh — pod chukwa-67758ff9cd-r5qtv rolled cleanly, /healthz returns 200.
Lib tests: 338 baseline → 339 after (one new test).
New test: ticket_detail_history_shows_relative_age_next_to_timestamp
<span class="sub">(3h ago)</span> annotation.(just now).All 339 tests pass under rust:1.88-bookworm.
$ curl -s https://chukwa.benac.dev/tickets/6c56541f-7e9a-4b1b-94d6-d29589811ebf | grep -oE '[0-9]+[hdmwy] ago|just now' | head -10
12m ago
9m ago
12m ago
11m ago
9m ago
$ curl -s https://chukwa.benac.dev/tickets/6c56541f-7e9a-4b1b-94d6-d29589811ebf | grep -oE 'class="sub">\([^<]+\)' | head -8
class="sub">(3 events)
class="sub">(12m ago)
class="sub">(11m ago)
class="sub">(9m ago)
The three (Nm ago) annotations correspond to the three history events on this ticket; the (3 events) line is the pre-existing history-count subtitle and is unrelated.
Scenario-store work continues in /tmp/chukwa-store on a separate branch and was not touched by this deploy. The two changes share no files; this rollout was independent as authorized.
this is the area where I want to see that extra info:
"
Picked up. Per directive, spawning a separate subagent in its own worktree (branched from main, not from the in-flight scenario-store branch). Subagent will: find the ticket-history rendering in src/html.rs, add relative-age strings using the existing humanize_age helper (already used for ticket-level created/updated), test, merge, deploy independently of the scenario-store work in flight, smoke-verify, propose resolution. ETA short — pure UI change, no schema or kernel touches.
Relative-age strings now render next to every ticket history timestamp; deployed independently. See proposed_resolution for transcript.
Caller accepted the proposed resolution.
Sign in as a human to drive this ticket from the page, or use the MCP tools.
Ticket created: Add timing information to ticking UI