Generate live sync report from Integration Settings page
Request Add an option on the Integration Settings page to generate a live sync report on demand, so users can adjust settings and immediately see the effect without leaving the settings page. Source Requested by Roel Vanderwegen in #proj-cow:
Roel 9 days ago
COW
Generate live sync report from Integration Settings page
Request Add an option on the Integration Settings page to generate a live sync report on demand, so users can adjust settings and immediately see the effect without leaving the settings page. Source Requested by Roel Vanderwegen in #proj-cow:
Roel 9 days ago
COW
Integrations sync page, add auto refresh to the status
Summary On the Integrations sync page, add auto-refresh for the sync status so users don't have to manually reload to see current state. Source #proj-cow — RVD, 2026-07-09
Roel 17 days ago
COW
Integrations sync page, add auto refresh to the status
Summary On the Integrations sync page, add auto-refresh for the sync status so users don't have to manually reload to see current state. Source #proj-cow — RVD, 2026-07-09
Roel 17 days ago
COW
Auto-redirect to logon/root after coming back to the tab after a long time
Summary When a user leaves the CoW admin portal tab open and returns after an extended period (session/token likely expired), the app should auto-redirect to the logon page (or root) instead of showing a stale/broken state. Source #proj-cow — RVD, 2026-07-09
Roel 17 days ago
COW
Auto-redirect to logon/root after coming back to the tab after a long time
Summary When a user leaves the CoW admin portal tab open and returns after an extended period (session/token likely expired), the app should auto-redirect to the logon page (or root) instead of showing a stale/broken state. Source #proj-cow — RVD, 2026-07-09
Roel 17 days ago
COW
COW: Build out email notifications functionality (user-facing)
Summary Build out email notifications functionality for CoW — user-facing notifications, distinct from the support form / existing-functionality verification tracked separately. Context Email sending is built in — permissions already granted to the managed identity (confirmed by John Duprey, 2026-07-08). This item is about surfacing that capability as actual user-facing notifications (e.g. alerts, status updates), not just verifying the underlying send mechanism. Related/dependent: the vendor API failure monitoring idea (separate ticket) plans to route its alerts through this notification capability. Source #proj-cow — RVD, 2026-07-08 #proj-cow — RVD confirms distinct scope, 2026-07-08
Roel 18 days ago
COW
COW: Build out email notifications functionality (user-facing)
Summary Build out email notifications functionality for CoW — user-facing notifications, distinct from the support form / existing-functionality verification tracked separately. Context Email sending is built in — permissions already granted to the managed identity (confirmed by John Duprey, 2026-07-08). This item is about surfacing that capability as actual user-facing notifications (e.g. alerts, status updates), not just verifying the underlying send mechanism. Related/dependent: the vendor API failure monitoring idea (separate ticket) plans to route its alerts through this notification capability. Source #proj-cow — RVD, 2026-07-08 #proj-cow — RVD confirms distinct scope, 2026-07-08
Roel 18 days ago
COW
COW: Ongoing follow up with Carbon on making their API work with our setup
Summary Ongoing follow up with Carbon on making their API work with our setup. Source #proj-cow — RVD, 2026-07-08
Roel 18 days ago
COW
COW: Ongoing follow up with Carbon on making their API work with our setup
Summary Ongoing follow up with Carbon on making their API work with our setup. Source #proj-cow — RVD, 2026-07-08
Roel 18 days ago
COW
COW: Add email support form + verify existing email functionality
Request Add an email support form / email functionality to CoW so support requests carry more context. Background RVD asked John Duprey about email testing done previously ("way back") — unclear whether that was a separate app or permissions added directly to the function app. This needs to be re-tested/confirmed as part of building the support form. Ask Confirm/re-verify the existing email functionality (standalone app vs. function app permissions) Build a support mail form so users can submit additional context Source
Roel 18 days ago
COW
COW: Add email support form + verify existing email functionality
Request Add an email support form / email functionality to CoW so support requests carry more context. Background RVD asked John Duprey about email testing done previously ("way back") — unclear whether that was a separate app or permissions added directly to the function app. This needs to be re-tested/confirmed as part of building the support form. Ask Confirm/re-verify the existing email functionality (standalone app vs. function app permissions) Build a support mail form so users can submit additional context Source
Roel 18 days ago
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 8 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 8 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 9 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 9 months ago
COW