Closed MarianRaphael closed 11 months ago
Thanks for the designs. Looks good!
To scope this back, we can for now, not bother with the Team-level screens, Device Groups 9as first iteration) can be Application-level configured only.
In a meeting between @MarianRaphael, @Steve-Mcl and myself we've agreed with this scope as first iteration. There was discussion around moving everything to live within the scope of DevOps pipelines only, but this would be just as much development effort, without a single view of Device Groups which would hinder UX.
@joepavitt could do with a bit of a leg up here.
The screenshots all seem to show management at team level (the Devices
menu level is highlighted in all)
I feel there is a screenshot design missing on how the Application shows its device groups?
this was the missing screenshot (it's all available in the Figma I linked to, and the prototype)
Thanks (and apologies for not digging) @joepavitt
After some discussion with @joepavitt there is a slight change in direction on the Device Membership Management.
[Remove]
(greyed out by default) and [Add]
[Remove]
will become enabled when 1 or more [x] check boxes are selected. Also, its text will be updated to indicate how many devices will be removed e.g. [Remove (6)]
[Remove]
will update the group's device membership by removing the [x] checked items[Add]
will replace the "Member Devices" table and show the "Available Devices" table in the same view
[Confirm]
button will be presented that will perform the membership update and close the "Available Devices" view, returning the user to the (updated) "Member Devices" view[Cancel]
button will presented that will simply revert to the "Member Devices" table view[Save Changes]
that commits the modifications to the DB in one go. (figma)
Original Design
https://www.figma.com/file/rMB2w5ZZUtTC0nxbwLYKJY/FlowForge-Platform?type=design&node-id=2528-18633&mode=design&t=UtJNcyM8PnopNmc5-0
Task
Based on our discussion, there is a need for a new design scope around the Device Group concept in #2997