Meet the new BigPicture navigation
A faster, smarter, and more intuitive way to work is here. We’ve redesigned BigPicture navigation to give you a smoother experience and better access to what matters most.
→ Discover what’s new, explore key improvements, and review feature name updates on the New navigation page.
→ The rollout will happen gradually, and the previous navigation will be retired in September 2026.
Sub-scope
Sub-scope (old navigation)
About the sub-scope definition type
When the scope definition is set to sub-scope, the box scope is always a subset of the scope already defined at an upper level of the box hierarchy (the upper-level box must have own scope). It can be automatically synced with a value of a selected field.
Example: A sub-scope box may be a parent when the box type is SAFe® Agile Release Train (ART). This box type comprises three levels of boxes, and the following structure is possible:
First-level box: own scope
Second-level box: sub-scope
Third-level box: sub-scope
The second-level sub-scope box is a parent for the third-level box, but the first-level box is always set to own scope).
The boxes with sub-scope display the tasks already added to a higher-level box with own scope. Any task added to a box with a sub-scope is automatically added to an upper-level box with the own scope.
Box configuration refers to the settings of a single, individual box. They are dependent on the box type settings. See the https://appfire.atlassian.net/wiki/spaces/SPMDRAFT/pages/1858864073/Scope+definition+box+types?force_transition=71b47b01-cff8-41bd-bee2-c5d1099fd965 page for more information.
Scope definition elements
Scope of the context box
The scope of the box you're configuring can be managed at the top part of the page.
Scope of the sub-boxes
Switch between levels of child boxes
Basic info and status of child boxes
Security roles
Users of sub-boxes with sub-scope can make any changes that match their permissions in a given sub-box, even if they lack appropriate permissions to their own scope box.
Those operations include:
Create tasks
Add tasks to own scope as manually added
Delete tasks
View tasks
If Angela is a Viewer in the Program-type Box ("own" scope) but is an Admin in an Iteration sub-box ("Sub" scope), she can execute all Admin operations on the Iteration tasks.
This means she effectively has Admin powers over some tasks from the Program-type box.
Automatic timeboxes (synchronize Jira sprints)
Go to the Timeboxes page to find out more about synchronizing Jira sprints
Sub-scope (new navigation)
About the sub-scope definition type
When the scope definition is set to sub-scope, the box scope is always a subset of the scope already defined at an upper level of the box hierarchy (the upper-level box must have own scope). It can be automatically synced with a value of a selected field.
Example: A sub-scope box may be a parent when the box type is SAFe® Agile Release Train (ART). This box type comprises three levels of boxes, and the following structure is possible:
First-level box: own scope
Second-level box: sub-scope
Third-level box: sub-scope
The second-level sub-scope box is a parent for the third-level box, but the first-level box is always set to own scope).
The boxes with sub-scope display the tasks already added to a higher-level box with own scope. Any task added to a box with a sub-scope is automatically added to an upper-level box with the own scope.
Box configuration refers to the settings of a single, individual box. They are dependent on the box type settings. See the https://appfire.atlassian.net/wiki/spaces/SPMDRAFT/pages/1858864073/Scope+definition+box+types?force_transition=71b47b01-cff8-41bd-bee2-c5d1099fd965 page for more information.
Scope definition elements
Scope of the context box
The scope of the box you're configuring can be managed at the top part of the page.
Scope information of boxes nested under the box you are currently configuring can be found at the bottom part of the page:
Scope of the sub-boxes
Scope information of boxes nested under the box you are currently configuring can be found at the bottom part of the page:
Switch between levels of child boxes
Basic info and status of child boxes
Security roles
Users of sub-boxes with sub-scope can make any changes that match their permissions in a given sub-box, even if they lack appropriate permissions to their own scope box.
Those operations include:
Create tasks
Add tasks to own scope as manually added
Delete tasks
View tasks
If Angela is a Viewer in the Program-type Box ("own" scope) but is an Admin in an Iteration sub-box ("Sub" scope), she can execute all Admin operations on the Iteration tasks.
This means she effectively has Admin powers over some tasks from the Program-type box.
Automatic timeboxes (synchronize Jira sprints)
Go to the Timeboxes page to find out more about synchronizing Jira sprints