The Scope 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 serves as a scope base for sub-scopes. Automatic rules can sync it. Use it when you want to be able to define and extend the scope of a Box 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 this setting to organize Boxes into portfolios, programs etc. The scope is always a sum of the scopes of the sub-Boxes in the Box hierarchy.


You won’t be able to adjust those settings after a Box has been created. Changes of the Scope definition don’t apply to existing Boxes of a given type. When a new Box is created, the scope settings are based on the scope definition of a Box type - there is no way to manually override individual scope settings of an existing Box.

Keep in mind:

  • 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 .
  • Box configuration refers to 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.
  • For a given Box type, you can modify the default Scope definition settings in the App's drop down at the top > Administration > Box type > edit (click on a Box type name) > Tasks > Scope definition.
 Click here to expand...




Scope types

Own scope 

Select the the "Own scope", so that users can add new tasks to the scope. Anyone with a Box Admin security role can adjust a 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. Additionally, you may add elements representing Versions, Components, Sprints, Projects, and Backlog by simply selecting appropriate Task types. Those items will be represented in the task hierarchy and can be used to organize the task structure.

Boxes with such 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 in Box types page. Scope of individual Boxes with "Own" scope can be edited by:

  • a Box admin
  • Jira admin (every Jira admin has full access to the App and can edit configuration of Boxes)
  • BigPicture admin (the role of App admin is granted in the App's drop-down > Administration > Security - every App admin can access and edit all Boxes in the App)

For example: The "PI planning (Smart house project)" has the scope type set to "Own scope"; therefore, you can define the scope of an individual Box based on Jira Projects, Boards, etc.

Users with a Box editor security role can impact the Box scope by creating new tasks using the "+" Tasks button (however, they can't access the "Scope definition" settings):

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). Go to configuration of a given Box to adjust the Box Scope definition (keep in mind, the tab doesn't provide the same functionality as it would in a Box with Own scope). A Sub-scope can be bidirectionally 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 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 then simply putting a task in a labeled container. All scheduling rules come together to determine how time 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'. The Box admin can not 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 at all (can't be found in Box configuration), 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 such scope type show the aggregated status and time tracking reports in the Hierarchy mode of the Overview module.

When you select this type, the Scope definition tab is hidden (can't be accessed in Box configuration > Task).


For example: You want to create a Portfolio overview and group several Project Boxes in the Overview module. As your task 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.