Mismatch between sync summary (“X successful”) vs. device table results and warranty expiry counts
When syncing additional devices, the sync summary reports “5 sync successful, 0 errors.” However: The Devices table shows 4 warranty results and 1 device where warranty could not be retrieved. The sync summary appears to count all 5 as “successful,” even though one device returned no warranty information. The warranty status counts (e.g., “Expired: 4”) also include the device where warranty data could not be retrieved, even though it is not actually “expired”. This creates a mismatch between what the UI reports and what the user sees in the device table. It is unclear to the user whether the missing warranty is being treated as: A non-error, A partial success, Or an expired device. Expected Behaviour Sync summary should reflect the actual outcomes: Successful warranty lookups (returned valid data) Devices where warranty info could not be retrieved (out of scope device) “Could not get warranty info” should not be counted as expired Warranty summary counts should match the table breakdown Licensing/device counts should treat no-data devices consistently and transparently
purfektblyss 4 months ago
Bug / Fix
COW
Mismatch between sync summary (“X successful”) vs. device table results and warranty expiry counts
When syncing additional devices, the sync summary reports “5 sync successful, 0 errors.” However: The Devices table shows 4 warranty results and 1 device where warranty could not be retrieved. The sync summary appears to count all 5 as “successful,” even though one device returned no warranty information. The warranty status counts (e.g., “Expired: 4”) also include the device where warranty data could not be retrieved, even though it is not actually “expired”. This creates a mismatch between what the UI reports and what the user sees in the device table. It is unclear to the user whether the missing warranty is being treated as: A non-error, A partial success, Or an expired device. Expected Behaviour Sync summary should reflect the actual outcomes: Successful warranty lookups (returned valid data) Devices where warranty info could not be retrieved (out of scope device) “Could not get warranty info” should not be counted as expired Warranty summary counts should match the table breakdown Licensing/device counts should treat no-data devices consistently and transparently
purfektblyss 4 months ago
Bug / Fix
COW
Devices and sync status show stale data after purge until manual refresh
After using Settings → Purge Devices, the UI does not immediately reflect the updated state. Both the Devices table and the sync status panel display outdated or incomplete information until the user manually refreshes the page. Observed behaviours: 1. Devices still appear after purge After purging, navigating back to the Devices page still shows the old devices. Only after a full browser refresh do the purged devices disappear from UI 2. Re-sync shows incorrect sync status After purge + "Sync Devices": Sync status panel gets stuck at 0% (“We’re working on it”). Meanwhile, the Logs page shows a full successful sync: PSA sync completed Devices added Warranty sync completed Sync completed successfully This means the backend completed everything, but the UI did not update to reflect completion. 3. Devices table and header become inconsistent The header sometimes shows “Found 3 of 3”, while the table displays “No records to display”. After refreshing the page, all devices appear correctly. This confirms the UI is rendering stale state instead of re-fetching current data. Expected Behaviour After purge, returning to the Devices page should show an empty list (or whatever the correct state is) without requiring manual refresh. After re-sync, the sync status panel should update from 0% → 100% and show completion when the backend has completed all tasks without refresh needed. Device header counts and table rows should remain consistent. For Review Does purge trigger any state or cache invalidation events? Is the Devices page using a cached result instead of re-querying the backend? Is the sync status component listening for the correct completion events after a purge? Are different parts of the UI using different sources or timings for device counts vs. device rows? Confirm whether the frontend needs: A re-fetch on navigation A state reset after purge Additional invalidation logic after sync completion Acceptance Criteria Devices page always shows accurate post-purge state without manual refresh. Sync status updates correctly during and after sync. No UI state where: Sync appears stuck at 0% while backend completed, or Header says “Found X of X” but table is empty. Navigating or returning to the Devices page always reflects the real device table state.
purfektblyss 4 months ago
Bug / Fix
COW
Devices and sync status show stale data after purge until manual refresh
After using Settings → Purge Devices, the UI does not immediately reflect the updated state. Both the Devices table and the sync status panel display outdated or incomplete information until the user manually refreshes the page. Observed behaviours: 1. Devices still appear after purge After purging, navigating back to the Devices page still shows the old devices. Only after a full browser refresh do the purged devices disappear from UI 2. Re-sync shows incorrect sync status After purge + "Sync Devices": Sync status panel gets stuck at 0% (“We’re working on it”). Meanwhile, the Logs page shows a full successful sync: PSA sync completed Devices added Warranty sync completed Sync completed successfully This means the backend completed everything, but the UI did not update to reflect completion. 3. Devices table and header become inconsistent The header sometimes shows “Found 3 of 3”, while the table displays “No records to display”. After refreshing the page, all devices appear correctly. This confirms the UI is rendering stale state instead of re-fetching current data. Expected Behaviour After purge, returning to the Devices page should show an empty list (or whatever the correct state is) without requiring manual refresh. After re-sync, the sync status panel should update from 0% → 100% and show completion when the backend has completed all tasks without refresh needed. Device header counts and table rows should remain consistent. For Review Does purge trigger any state or cache invalidation events? Is the Devices page using a cached result instead of re-querying the backend? Is the sync status component listening for the correct completion events after a purge? Are different parts of the UI using different sources or timings for device counts vs. device rows? Confirm whether the frontend needs: A re-fetch on navigation A state reset after purge Additional invalidation logic after sync completion Acceptance Criteria Devices page always shows accurate post-purge state without manual refresh. Sync status updates correctly during and after sync. No UI state where: Sync appears stuck at 0% while backend completed, or Header says “Found X of X” but table is empty. Navigating or returning to the Devices page always reflects the real device table state.
purfektblyss 4 months ago
Bug / Fix
COW
Improve UI feedback when clicking “Get Warranty” so users know what’s happening
When a user clicks Get Warranty, the system shows a log entry like: “Added X devices to the update warranty queue.” But from the user’s point of view there is: no visual indication that anything is currently processing. no progress or status showing when their request actually starts running. no clear signal when the warranty check has finished or whether the system decided no update was needed. This creates uncertainty about whether the action succeeded or is still running, leaving users are unsure if they should wait, refresh, or expect results somewhere else. User Story As a user, I want clear visual feedback when I click Get Warranty, so I understand: That my devices were added and are now being processed. That something is actively happening in the background. When the warranty check is complete (or if no changes were needed). This will help me know whether the system is working and when I should expect results. Acceptance Criteria Users receive immediate confirmation that their request was accepted. Users can see that the system is currently working on the warranty updates. Users receive a clear completion message when processing is finished. Users do not have to check logs or guess what happened.
purfektblyss 4 months ago
Enhancement
COW
Improve UI feedback when clicking “Get Warranty” so users know what’s happening
When a user clicks Get Warranty, the system shows a log entry like: “Added X devices to the update warranty queue.” But from the user’s point of view there is: no visual indication that anything is currently processing. no progress or status showing when their request actually starts running. no clear signal when the warranty check has finished or whether the system decided no update was needed. This creates uncertainty about whether the action succeeded or is still running, leaving users are unsure if they should wait, refresh, or expect results somewhere else. User Story As a user, I want clear visual feedback when I click Get Warranty, so I understand: That my devices were added and are now being processed. That something is actively happening in the background. When the warranty check is complete (or if no changes were needed). This will help me know whether the system is working and when I should expect results. Acceptance Criteria Users receive immediate confirmation that their request was accepted. Users can see that the system is currently working on the warranty updates. Users receive a clear completion message when processing is finished. Users do not have to check logs or guess what happened.
purfektblyss 4 months ago
Enhancement
COW
Planned
Improve manufacturer detection
Long term item. Needs some serious brainstorming. As a bandaid fix we now prioritize the manufacturer from the PSA
Roel 4 months ago
COW
Planned
Improve manufacturer detection
Long term item. Needs some serious brainstorming. As a bandaid fix we now prioritize the manufacturer from the PSA
Roel 4 months ago
COW