Introduction
A defined collection of tasks makes up the box scope. In general, tasks can be added to the scope manually or get automatically synchronized with connected tools such as Trello.
...
Security and access
To access the Scope definition section at the box configuration level:
...
Scope definition element or action | Description |
|---|
Scope of the context box | The scope of the box can be managed at the top part of the page. If the box has scope set to own, you can define its elements at the top part of the page. Sub-scope can be managed in a context box (the box you are in) or in a parent box under the Timeboxes section below. If the box has scope set to sub-scope, you can only set synchronization rules.
|
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. Depending on the scope type of a child box, you can see: When a child box is set to be a sub-scope, you can see synchronization rules. When a child box has own scope, you are informed about it. The link in the message redirects to the configuration page for the relevant box scope. When a child box functions as a portfolio and has a scope set to none, you can see a message.
|
Switch between levels of child boxes | Using the arrows you can switch between viewing the level of children and grandchildren in a given box. |
Basic info and status of child boxes | Click the … icon to: |
Own scope
Box admins can:
...
Role or element | Description |
|---|
Scope owner | The scope owner is listed as the first field in the Automatic rules section. A box can contain only the items the scope owner can access (viewing access is sufficient). If add items the scope owner does not have access to, you cannot save the scope. The scope owner does not have to be an actual user added to the box in any capacity (does not have to be a box admin, box editor, or box viewer). Permissions of the scope owner user account within the external tool are the basis for the sync of tasks. Tasks are pulled into the scope of a box only if the scope owner can access them (at least as a viewer). When connecting with tools such as Trello, you need to specify the scope owner for each connection. You cannot change the scope owner once a connection is established.
|
Scope filters | If tasks are already created in Jira, you can define the scope using the following filters: Boards - select from the list created Jira Board (Kanban and Scrum board). JQL filters - select from the list of previously saved JQL filters. Projects - select from the list of available projects.
If you connect with Trello, you can only select Trello boards. You can select multiple items and increase the number of issues within the scope, as the OR operator is used for boards, filters, and projects.
|
...
Element | Description |
|---|
Manually added tasks | The section remains hidden until needed. It is visible only when it contains at least one task. Manually added tasks are the ones that do NOT fit the scope filter. A box admin can erase all the tasks in the section by clicking the Eraser icon.
|
Manually removed tasks | |
Task types | You can select elements to be displayed as tasks and, when possible, synchronized with a connected tool (such as Jira). Task types are added automatically when respective structure builders are activated. For example, enabling the sprint structure builder adds the sprint task. Additional elements are added as basic tasks (since they do NOT exist as Trello Cards, they must be added in some form to be part of the task structure). In the case of Trello, you can add the following: Cards Lists Check items Boards Checklists
|
...