steve/restic-manager
1
0
Fork 0
Code Issues Pull Requests Actions Projects Releases 5 Wiki Activity

Agent updates: refresh resets filters and host filtering is ineffective #50

New Issue
Closed
opened 2026-08-22 12:01:40 +01:00 by steve · 1 comment
steve commented 2026-08-22 12:01:40 +01:00
Owner
Copy Link
Copy Source

Problem

The new Agent updates screen is difficult to use because its automatic refresh resets operator input and the host filters do not affect the displayed results.

Current behaviour

  1. The rollout action requires the operator to type the selected host count into "Type selected count to confirm". This duplicates the existing selection/confirmation step and is unnecessary.
  2. While entering a value in Filter name or Version, or choosing a state filter, the periodic refresh resets the controls to their defaults after roughly one second.
  3. Even when a state can be selected before the refresh, the visible host list does not change. For example, selecting Eligible continues to show ineligible hosts as well.

Expected behaviour

  • Remove the typed selected-count confirmation requirement.
  • Background refreshes must preserve all in-progress filter values and selections.
  • Name, version, and state filters must immediately and correctly constrain the displayed host list.
  • Selecting Eligible must display eligible hosts only.
  • Refreshing fleet data must not replace locally controlled form/filter state.
  • The selected-host count and rollout summary should remain accurate for the filtered/selected hosts.

Acceptance checks

  • Type slowly into Filter name and Version across multiple refresh intervals; the entered text remains intact.
  • Select each available state and verify only matching hosts are displayed.
  • Combine name, version, and state filters and verify their intersection is displayed.
  • Select hosts, allow a refresh to occur, and verify the intended selection remains stable where those hosts still exist.
  • Start the rollout confirmation flow without being asked to retype the selected host count.

Observed in release v1.2.0.

## Problem The new **Agent updates** screen is difficult to use because its automatic refresh resets operator input and the host filters do not affect the displayed results. ### Current behaviour 1. The rollout action requires the operator to type the selected host count into **"Type selected count to confirm"**. This duplicates the existing selection/confirmation step and is unnecessary. 2. While entering a value in **Filter name** or **Version**, or choosing a state filter, the periodic refresh resets the controls to their defaults after roughly one second. 3. Even when a state can be selected before the refresh, the visible host list does not change. For example, selecting **Eligible** continues to show ineligible hosts as well. ### Expected behaviour - Remove the typed selected-count confirmation requirement. - Background refreshes must preserve all in-progress filter values and selections. - Name, version, and state filters must immediately and correctly constrain the displayed host list. - Selecting **Eligible** must display eligible hosts only. - Refreshing fleet data must not replace locally controlled form/filter state. - The selected-host count and rollout summary should remain accurate for the filtered/selected hosts. ### Acceptance checks - Type slowly into **Filter name** and **Version** across multiple refresh intervals; the entered text remains intact. - Select each available state and verify only matching hosts are displayed. - Combine name, version, and state filters and verify their intersection is displayed. - Select hosts, allow a refresh to occur, and verify the intended selection remains stable where those hosts still exist. - Start the rollout confirmation flow without being asked to retype the selected host count. Observed in release **v1.2.0**.
steve closed this issue 2026-08-22 12:06:45 +01:00
steve reopened this issue 2026-08-22 12:31:12 +01:00
steve commented 2026-08-22 12:31:19 +01:00
Author
Owner
Copy Link
Copy Source

Reopened after local validation showed that preserving state across each three-second panel replacement still caused dropdown collapse and visible input flicker. The corrected approach is to remove polling entirely while selecting/filtering hosts and retain it only while a rollout is actively running. This keeps filtering purely client-side and prevents any idle form DOM replacement.

Reopened after local validation showed that preserving state across each three-second panel replacement still caused dropdown collapse and visible input flicker. The corrected approach is to remove polling entirely while selecting/filtering hosts and retain it only while a rollout is actively running. This keeps filtering purely client-side and prevents any idle form DOM replacement.
steve closed this issue 2026-08-22 12:33:46 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
enhancement
New feature or improvement to existing functionality
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
steve
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: steve/restic-manager#50
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?