Moving a Box to a different place in a hierarchy results in a change of its parent. The App verifies if the current scope settings of the new parent Box are compatible with the sub-Box + checks the Box type parent settings. To move a Box, you must have sufficient permissions in both Boxes (parent and child).
Your ability to move a Box depends on:
- security roles
- In Box type configuration, you decide possible parents of each Box type. Parent Box types determine how you can build the Box hierarchy (nest Boxes) and prevent users from making mistakes and mixing methodologies.
- Each Box type has Scope type settings (None, Own scope, Sub-scope).
- Sequentiality (Box type settings)
- Box period mode
- Box status (under a "closed" Box you can place only other "closed" Boxes)
Security and access
You need sufficient security role permissions in both the Box that is being moved and the Box that will become the new parent in the hierarchy.
- You have to be an Admin of the Box that is being moved (keep in mind, since roles are inherited, if you are an Admin in an upper-level Box, you are automatically an Admin of all sub-Boxes lower in the hierarchy).
- The App admin has full permissions in all Boxes and can perform the action.
- In the new upper-level (parent) Box, you must be an Admin or a sub-Box creator (once again, Admin role can be inherited from an upper-level Box. Sub-Box creator role is not inherited).
For example, Paul is an Admin of "ALFA" but only an Editor of "OMEGA." He will not be able to move "ALFA" and nest it under "OMEGA" - his current set of permissions is insufficient.
Remember to adjust possible parents for each Box type. If the list of possible parents doesn't allow the change, you won't be able to move a Box. Settings of a Box type have to allow for a new parent relationship.
For example, Drew is an App admin, so he has full Admin access to all Boxes. However, when he tries to place the "ALFA" Box in "OMEGA," he can't do it. "ALFA" is an "Agile Project" Box type and can't be placed under "OMEGA" (the "Program" Box type).
For this move to be possible, a new parent would have to be added for the "Agile Project" Box type.
Under a "Closed" parent Box you can place only other "Closed" Boxes.
|parent "Not started"||parent "In progress"||parent "Closed"|
|child "Not started"|
|child "In progress"|
In general, if moving a Box would drastically impact its scope, the change will not be permitted. This means that Boxes with the "Sub-scope" cannot be moved in the hierarchy, as their scope depends entirely on their parent; all work done in Boxes with "Sub-scope" is intrinsically tied to the upper-level Box. Boxes that utilize the "Sub-scope" have to be created directly where you intend to use them. You can find more information about the scope types here.
Under Boxes with "None" scope, you can place:
- other Boxes with "None" scope
- Boxes with "Own" scope
Under Boxes with "Own" scope you can place:
- Boxes with "None" scope
- other Boxes with "Own scope"
Take a look at the matrix below to see what kinds of changes are possible:
The scope type is set during Box creation - it is based on the Box type settings and can't be changed afterwards.
For example, the "Program Increment" Box type is set to have a "Sub-scope." If Jessica tries to move a "Program Increment 4" from one Box to another, she won't do it.
Sequentiality settings affect same-level Boxes (can potentially prevent Box periods from overlapping).
Auto bottom-up and auto scope-based Boxes are never sequential - they can always overlap.
Only "manual" and "auto top-down" Boxes can be sequential - if set to 'sequential', same level sequential Boxes can't overlap.
Box type period mode can affect if a new child Box can be created with a specified start/date.
Period of a Box vs period mode of its sub-Boxes
Boxes in an "auto bottom-up" period mode are affected by the period of their sub-Boxes (regardless of a sub-Box period mode).
Period of a Box vs period mode of its parent
- An "auto top-down" parent →
- limits the period of an "auto top-down" child Box
- child Boxes in "manual"/ "auto scope-based" period mode are not affected
- "auto bottom-up" child overrides an "auto top-down" parent
Effects of the parent Box period mode on a child Box period are outlined in the table below.
Parent Box →
|auto bottom-up||unaffected (regardless of child period mode)|
|auto scope-based||unaffected (regardless of child period mode)|
An "auto top-down" parent limits the period of an "auto top-down" child
Period of an "auto bottom-up" child unaffected ("auto bottom-up" child has priority over an auto "top-down parent")
Periods of "manual" and "auto scope-based" Boxes unaffected
|manual||unaffected (regardless of child period mode)|
You can use the multi-select function to move multiple Boxes simultaneously. Validation is performed for each Box - if any of the Boxes can't be moved, the entire operation fails, and no Boxes are moved. In other words, the system will either successfully move all the Boxes or none at all.
For example, if Jessica creates a "Portfolio" (using a "Portfolio" Box type), she will be able to place both "ALFA" and "OMEGA" Boxes in it. "Portfolio" has "None" scope. "ALFA" and "OMEGA" were created with the "Own" scope. She can select them both and place them in the portfolio.
If any of the Boxes can't be moved, the entire operation fails (no Boxes will be moved), regardless of which validation check failed.
For example, the "CUSTOM" Box type can't be placed under "Portfolio."