ui(alerts): clarify Acknowledge vs Resolve #9

Merged

steve merged 2 commits from alerts-ack-resolve-clarity into main 2026-05-04 23:25:35 +01:00

Conversation 0 Commits 2 Files Changed 2

+14 -4

steve commented 2026-05-04 23:04:16 +01:00

Owner

Copy Link

Copy Source

Summary

User feedback: from the Open tab, Acknowledge and Resolve look
identical — both make the row disappear. The semantic difference only
shows up on the next fire of the same condition, which on a quiet
system is invisible.

This adds:

• A one-line legend under the page header summarising both actions.
• title= tooltips on each button covering the same ground for
  keyboard and assistive tech.

No behaviour change. Pure UI copy.

## Summary User feedback: from the Open tab, Acknowledge and Resolve look identical — both make the row disappear. The semantic difference only shows up on the *next* fire of the same condition, which on a quiet system is invisible. This adds: - A one-line legend under the page header summarising both actions. - title= tooltips on each button covering the same ground for keyboard and assistive tech. No behaviour change. Pure UI copy.

steve added 1 commit 2026-05-04 23:11:47 +01:00

ui(alerts): make Acknowledge vs Resolve distinction visible ... c446ca072e

Both buttons make the row leave the Open tab, so on a quiet system
they look identical. The behavioural difference only manifests next
time the underlying condition fires:

  - Acknowledge silences fan-out while the problem persists; the
    alert parks on the Acknowledged tab and recurrences just touch
    last_seen_at without re-notifying.
  - Resolve closes the alert. If the same condition fires again
    later, a fresh alert with a new id raises and the channels
    fan out as if it were the first time.

Add a one-line legend under the page header explaining both, and
title= tooltips on each button covering the same ground for keyboard
and assistive tech.

steve force-pushed alerts-ack-resolve-clarity from db0afe0ac9 to c446ca072e 2026-05-04 23:11:47 +01:00 Compare

steve added 1 commit 2026-05-04 23:22:45 +01:00

ui(alerts): drop 'Severity / kind' header — column shows kind only ... fc58e57598

The text in that column is the kind chip (backup_failed, etc).
Severity is encoded entirely in colour: severity dot, left-border
accent, and the chip's tint. The header promised both but only one
made it into text, which read as if the severity word should
appear too.

Header now reads 'Kind'. Colour does the severity work, as it
already did.

steve merged commit dd53c9e497 into main 2026-05-04 23:25:35 +01:00

steve referenced this issue from a commit 2026-05-09 14:23:46 +01:00

ui(alerts): clarify Acknowledge vs Resolve (#9)

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

No items

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

steve

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: steve/restic-manager#9