Scope definition (box types)

What is the scope definition?

The bcope type determines whether Box admins can define the scope of a created box. 

There are three different options:

• Own-scope - the box scope has a separate task structure and is a scope base for sub-scopes. Automatic rules can sync it. Use it to define and extend the box's scope by selecting tasks from Jira and connected tools. 

• 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.

• None -  the box scope cannot be defined. Currently, you can use such a box for calculating respective aggregates in the box hierarchy only (visible in the Overview module). Use it to organize boxes into portfolios, programs, etc. The scope is always a sum of the scopes of the sub-boxes in the box hierarchy.

Keep in mind:

• A box type contains the default settings applicable to multiple boxes (all boxes of a given type). Those settings are adjusted on the Administration > Box types page.

• Box configuration refers to the settings of a single, individual box. They are dependent on the box type settings. 

Security and access

Only the App admin security role can access and change the box type administration.

To access the box type settings:

1. Click the wrench icon at the top right and select Box types from the drop-down list.

2. Click a Box type name to select it and open its settings.

3. Go to Tasks > Scope definition tab.

Open

Scope types

Own scope 

Select own scope so that users can add new tasks to the scope. Anyone with a box admin security role can adjust the scope of a particular box in the Scope definition tab of box configuration.

In boxes with own scope, you can select items from the list of available Jira boards, previously saved JQL filters, or Jira projects. You may also add elements representing versions, components, sprints, projects, and backlog by selecting appropriate task types. Those items will be represented in the task hierarchy and can be used to organize the task structure.

Boxes with this scope type show the aggregated status and time-tracking reports in the Hierarchy mode of the Overview module.

You can find more information on configuring a box scope on the Scope definition page.

Scope of individual boxes with own scope can be edited by:

• Box admins

• Jira admins (every Jira admin has full access to the App and can edit the configuration of boxes)

• BigPicture admins (the App admin role is granted in Administration > Security)

For example, The SAFe ART (Smart house) has the scope type set to its own scope. Therefore, you can define the scope of an individual box based on Jira projects, boards, etc.

Open

Users with a box editor security role can impact the box scope by creating new tasks using the +Add task button (however, they can't access the Scope definition settings).

Sub-scope

When you select 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). A sub-scope can be bi-directionally synced with a selected field - assigning a task to a box will update the field with a respective value. Correspondingly, updating the field value of a task will result in automatically planning the task for a box. 

Depending on the settings, this can, for example, automatically adjust both the start and end date of a task, effectively moving it on a timeline and even changing its duration. Planning a task for a box can have a much bigger impact than simply putting a task in a labeled container. All scheduling rules come together to determine how periods of tasks added to the scope react to other changes (e.g., task dependencies or parent/child relationship in the task structure).

The field-based sync is applied only to tasks that are in the scope of the upper-level box (i.e., box with own scope).

When you select the sub-scope, a new section Sub-scope definition template appears so you can choose the field to synchronize with.

For example: The 'Program Increment 1' sub-box of the 'PI planning (Smart house project)' has the scope type set to sub-scope. A box admin cannot change the scope of the 'Program increment' but can configure the synchronization of the 'Iteration 1.1' sub-box.

None (aggregations only)

In this mode, the scope definition section doesn't exist on the Box configuration > Tasks page, as the scope is based strictly on all sub-boxes. You will not see any task in any of the modules because such scope type can only aggregate data - there is no need to add any tasks to the scope.

Boxes with this scope type show the aggregated status and time-tracking reports in the Hierarchy mode of the Overview module.
For example, you want to create a portfolio overview and group several project boxes in the Overview module. As your tasks are already included within the project boxes, there is no need to configure the scope. The portfolio structure will be reflected in the Overview module.