Preset Feature Feedback
What is the problem or goal you're trying to solve or accomplish?
Users managing dashboard styling need to safely maintain CSS templates without accidentally breaking or orphaning styling on live dashboards. Today they have no visibility into where a template is used and no safeguard when deleting one. Three gaps combine into a confusing experience:
A CSS template can be deleted even while it is actively applied to one or more dashboards, with no warning, confirmation detail, or list of affected dashboards.
After deletion, dashboards that used the template continue to display the styling, so the state of the template versus the dashboard becomes ambiguous.
There is no way to discover which dashboards reference a given template — no dependency tracking or back-reference exists.
The goal is predictable lifecycle management: know what a template affects before deleting it, and understand what happens to that styling afterward.
How are you solving it currently?
Manually. Users have no in-product way to map templates to dashboards, so they either avoid deleting templates entirely, or delete and then manually inspect dashboards one by one to check whether styling changed. The "orphaned CSS" persists silently, so cleanup requires opening each dashboard's Properties → Styling and clearing the CSS text area by hand.
What is your recommended solution?
On delete, warn the user when the template is in use, e.g. "This template is currently applied to X dashboard(s). Are you sure you want to delete?"
Optionally list (and link to) the affected dashboards.
After deletion, either (a) remove the CSS from affected dashboards, or (b) clearly flag the remaining styling as "orphaned" custom CSS so the state is unambiguous.
Provide dependency tracking so users can see which dashboards reference a template.
