FlowFuse
Device Groups: improve UX of working with large groups
Description
This Epic is to collate tasks related to improving the UX around device groups - in particular device groups with a large number of members.
Adding a duplicate of comment: https://github.com/FlowFuse/flowfuse/issues/6006#issuecomment-3422983450 here sine it will be lost when its PR is merged.
Apologies for being Late to the party, but we started adding batch management to devices for scaling up.
I am wondering why we are not building on that?
For example, an obvious QoL improvement would be to permit bulk ops for adding to / removing from group in the Actions drop down like we do for assignment?
Mock:
The iteration we have taken with #6124 seems like more work with less benefit?
The iteration we have taken with https://github.com/FlowFuse/flowfuse/issues/6124 seems like more work with less benefit?
This was driven by specific customer feedback around how awkward it is to manage device membership for individual devices. And that the expectation was to be able to manage properties of a device from the device's own page.
The bulk use case is also valid, just different.
@cstns please raise an issue for Steve's suggestion and size appropriately.
