-
Epic
-
Resolution: Done
-
Normal
-
None
-
Workspace movement feature
-
Product / Portfolio Work
-
False
-
-
False
-
Unset
-
Done
-
CRCPLAN-357 - Management Fabric | M2 - Hierarchical Workspaces and Access Inheritance
-
0% To Do, 0% In Progress, 100% Done
-
-
Review the CRCPLAN parent feature for additional context, including the feature overview, goals, user stories and use cases, acceptance criteria, designs, dependencies, risks, assumptions, pending questions and documentation callouts.
Summary and goal
As a Workspace Administrator, I want to be able to move a workspace to a new parent workspace within the Organization so I can reorganize workspaces to better reflect my company's structure and workflows.
Acceptance Criteria
- Workspace Administrator can move a workspace to a new parent.
- Movement operation result with removing old workspace parent relations and add new parent relations
- (Validation) Workspace Administrator cannot move workspace to
- Ensuring a Workspace cannot be:
- Infinitely recursive (e.g. Moved to own descendants, moved to the same workspace, moved to the same parent)
- [Temporary through M5] Moved to a parent that is not either the Default workspace, or within the Default workspace
- Moved to a level that exceeds the depth limit (nested 4)
- Moved to the parent workspace that already has a workspace with the same name
Checklist
Checklist Item | Required | Notes or Comments |
---|---|---|
Workstream or external team dependencies? | Y / N | |
ADR Required?
|
Y / N | |
Testing plans
|
Y / N | |
Known dependencies?
|
Y / N |
- blocks
-
RHCLOUD-40433 Create new action move workspace
-
- Closed
-
- relates to
-
RHCLOUD-40190 Support Hierarchy under default workspace
-
- Closed
-