Is your feature request related to a problem? Please describe.
Basically when creating a maintenance window for multiple monitors, the app creates one database record per monitor. This results in multiple rows with the same name, same schedule, and same settings appearing in the maintenance windows table , one per monitor. This is confusing and hard to manage, especially at a larger scale.
Describe the solution you'd like
The maintenance windows table should display one row per logical window (grouped by name/schedule). Each row should be expandable to show the individual monitors it applies to, and allow managing them individually from there.
Suggested Fix
Either:
Group records client-side by name + start + end when displaying the table, or
Return pre-grouped data from the API
Additional context
Here is a screenshot of how many windows with same name and no grouping looks like:
Is your feature request related to a problem? Please describe.
Basically when creating a maintenance window for multiple monitors, the app creates one database record per monitor. This results in multiple rows with the same name, same schedule, and same settings appearing in the maintenance windows table , one per monitor. This is confusing and hard to manage, especially at a larger scale.
Describe the solution you'd like
The maintenance windows table should display one row per logical window (grouped by name/schedule). Each row should be expandable to show the individual monitors it applies to, and allow managing them individually from there.
Suggested Fix
Either:
Group records client-side by name + start + end when displaying the table, or
Return pre-grouped data from the API
Additional context
Here is a screenshot of how many windows with same name and no grouping looks like: