-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
False
-
None
-
False
-
Admin UXD Sprint 223, Admin Sprint 224, Admin Sprint 225, Admin Sprint 226
The 'Create workspace' flow has been explored in the past but needs to be determined how this works. Should it be a simple flow where the user just names the workspace, or should they also add services?
Open Questions:
- How will we surface the nesting and hierarchy relationships in the create modal?
- Do we want to help guide users into best practices somehow when it comes to compute vs service workspaces?
- What actions should be available when you create a workspace vs edit (addition additional services)?
Other notes:
- Based on the conversation during the stakeholder call on Aug 31 - it sounds like it would be nice to have a display name as well as a description field. Andy will put in a request for KCP to support spaces and capitalization.
Design doc: https://docs.google.com/document/d/1WULI_tE6s4osDnyrF4gLApG8e0F77vejPbCiHn1YeF4/edit?usp=sharing
- is related to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Closed
-