Sub-scope (scope definition)
- Magdalena Żaczek
Introduction
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.
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.
A "Box type" contains the default settings applicable to multiple boxes (all boxes of a given type). Those settings are adjusted in Box type Administration. Boxes can be created with different types of scope - those settings determine how a box can be configured and what can be done when defining a scope.
Box configuration refers to the settings of a single, individual box. They are dependent on the "Box type" settings.
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
For example:
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.