About BigPicture

BigPicture installation and updates

Quick start with BigPicture

BigPicture Sizing Guide

Cloud vs. Server - Key Differences in BigPicture on These Platforms

BigPicture Export

Progress Tracking

Tutorials and tips


 BigPicture 7.10 and earlier

Concept of a Program

Setting up BigGantt and BigPicture to support next-gen projects

 BigPicture release notes

BigPicture Cloud Backlog


About BigGantt

BigGantt installation and updates

Cloud vs. Server - Key Differences in BigPicture on These Platforms

 BigGantt release notes

 Release notes
 Jira Cloud

 Jira Server


 Jira Cloud

 Jira Server

 Jira Cloud

 Jira Server

 BigPicture Enterprise
 Jira Cloud

 Jira Server

Knowledge Base

Tutorials and tips

Data Scope is pretty much what makes our app a unique PPM powerhouse. In this tab we can select almost any piece of information stored within our Jira to be displayed on the Gantt chart. Starting from the very top, we have a wide range of scope defining attributes. These attributes describe what information exactly will be pulled and displayed in our Program from Jira and in what context we will operate.

Scope Context User

'Scope Context User' field allows to define a Jira user in whose context our data will be pulled from Jira environment. Whenever we create a Program either through Program Wizard or edit it in the Program Configuration, the Scope Context User has to be defined. Whichever piece of data this user might have in his range, it can be pulled into a scope of our Program. Later, thanks to other filtering features, we can narrow down the range of display, nevertheless we will never be able to add more data than the Scope Context User has in their scope, even if a scope of other users who interact with the Program is much wider.

At this point, it is also worth mentioning, that even if one of the Program participants has access to a set of data within Jira (Issues, Projects etc.), on the Gantt chart and Gantt's WBS it may not be displayed as they did not have enough permissions to edit or even display certain Tasks. Such obstacle is encountered whenever that specific Program's Scope Context User does not have enough permissions.

Please note that if there is applied "currentUser()" function within a JQL of any selected scope element (a board, a filter or an additional JQL), Scope Context User will be also used in this case while searching issues in Jira.


'Board' field allows you to define content of Jira Boards which you would like to view within our Program. Please remember though, that the Jira Board content has to be accessible to selected Scope Context User. As Programs work with tasks, it will be tasks that can be pulled from this Jira instance.


'Project' grants the possibility to select whole Jira Projects to view within our Program. It is possible to pull every single Project that is accessible to selected Scope Context User in order to view all tasks from selected Jira Project.


'Filter' field is pretty much self-explanatory as it lets every Jira issue that is already filtered out with JQL to be displayed as long as it is accessible to selected Scope Context User.

Extra Filtering Conditions

Once we choose all scope defining conditions, 'Extra Filtering Conditions' enable creating JQL filters on the spot – from the Program Configuration in order to narrow down the range of tasks that exist in our Program's Scope even further.

Thanks to such a wide range of scope defining capabilities, customizing eg. your Gantt chart to display the content to the accuracy of a single issue is a cakewalk!

Here's our video tutorial on that subject: