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 us 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 their range it can be pulled to 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 Program Participants has an access to a set of data within Jira (Issues, Projects etc.), on the Gantt chart and Gantt's WBS it may 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.
'Board' field allows us to define content of Jira Boards which we would like to view on our chart. Please remember though, that the Board has to be in the scope of our Scope Context User. As our Programs work with tasks, it will be tasks that can be pulled from this Jira entity.
'Project' grants us a possibility to select whole Jira Projects to view in our app's Gantt chart and Gantt's WBS. We can pull every single Project that is already in the scope of the selected Scope Context User in order to view all of them on the chart.
'Filter' field is pretty much self-explanatory as it will let us display every Jira issue that is already filtered out with JQL as long as it is within the scope of the Scope Context User.
Extra Filtering Conditions
Once we choose all scope defining conditions, 'Extra Filtering Conditions' will let us create 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 wide range of scope defining capabilities, we can customize our Gantt chart to display the content to an accuracy of a one issue!