Search

Content
 BigPicture

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

Integrations

 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

 BigGantt

About BigGantt

BigGantt installation and updates

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

 BigGantt release notes

Shortcuts
 Release notes
 BigPicture
 Jira Cloud

 Jira Server

 Trello

 BigGantt
 Jira Cloud

 Jira Server

 BigTemplate
 Jira Cloud

 Jira Server

 BigPicture Enterprise
 Jira Cloud

 Jira Server

Knowledge Base

Tutorials and tips

This section of the app was redesigned so if you are using BigPicture version earlier than 7.10 (or BigGantt 4.9.0) please use this link Program Configuration - General - Scope definition.

Defining the scope of the Program

Program's scope is defined by the range of data which Scope Owner has access to. Once you create the Program there are two options:

  • start adding tasks manually
  • add existing data to the Program.
FeatureDescription
Instance name

Name of the currently used Jira instance.

BigPicture 8 will allow you to sync with Trello boards and other Jira instances.

Scope Owner

A.k.a. Scope Context User - a user in whose context data (Jira issues) synced with Programs will be pulled to it, based on the scope and range of permissions which that specific user has.

Automatic rules

Sync the Program based on selected Boards, JQL filters or Projects.

Task types

It is possible to add Jira issue versions, components, sprints and backlog, or Projects as task.

In case of version and sprints, the start and end dates (release date in case of versions) will synchronize with Jira and other Program Boxes.

As Projects, backlogs and components do not have start and end dates the synchronization occurs between Program Boxes only.

To structure you tasks automatically based on the selected issue types go to Program Box configuration - Task - Task structure.

Manually added tasks

Manually added tasks are those which do not fit the scope filter but were added by the user using the app's modules +Task button (via Gantt and Board modules.

Earlier versions of the app had a 'Remove tasks not in filter' feature and all the tasks which do not fit the scope filters will be added to the "manually added task" list in this view.

Saving the scope

The app will validate the scope and if errors occur then saving the scope will be disabled.

If the scope is defined correctly (tasks exist and the filters are not corrupted or ) the total number of tasks will be displayed.

Saving will be disabled if one of the following occurs:

  • at least one item in the scope definition is incorrect or doesn't exist (for example: JQL Query is incorrect, Scope Owner doesn't exists, added Project doesn't exists, etc.)
  • total number of tasks is greater than the task limit set for Programs.

When the total of task exceeds 25000. a warning about the loading time will appear:

"X tasks in the scope. Synchronization may take a bit longer..."

The warning will appear in case the task limit in Technical configuration - General - Task configuration is not defined or exceeds 25000 tasks.

Duplicated tasks

When a task is added manually and updated such that it fits the filter described in Automatic rules section it will be classified as a duplicate (alternatively, when the Automatic rules are updated and manually added task now fits the filtering criteria).

Scope misconfiguration errors warnings

The warning states, that you have added a JQL to Program's scope a which leads to an item that does not exist (such as a filter or a project) or you don't have permission to access:

Warning

'Scope misconfiguration! A value with ID '10375' does not exist for the field 'id'. user: (...)

To avoid such warnings, run a JQL using Jira issue search first to see if the results are what you aim for in your Program.