Code Review
Dutch (Belgium) is missing from the Autopilot language selection
Can we get Dutch (Belgium) added in the Autopilot Profile Wizard Language selection.
Emile De Snoeck 20 days ago
Feature Requests
Code Review
Dutch (Belgium) is missing from the Autopilot language selection
Can we get Dutch (Belgium) added in the Autopilot Profile Wizard Language selection.
Emile De Snoeck 20 days ago
Feature Requests
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 6 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 6 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 6 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 6 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 6 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 6 months ago
COW