Content
 BigPicture

About BigPicture

BigPicture installation

Quick start with BigPicture

Roadmap module

 Scope module (BP 7)

Export in BigPicture

Tutorials and tips

Integrations

 BigPicture release notes

BigPicture Cloud Backlog


Shortcuts
 Release notes
 BigPicture
 Jira Cloud

 Jira Server

 Trello

 BigGantt
 Jira Cloud

 Jira Server

 BigTemplate
 Jira Cloud

 Jira Server

Knowledge Base

Tutorials and tips

Search

BigPicture and BigGantt pull the data straight from the Jira environment. While the process is fully automated for users' convenience, various parameters of each Program among many other things can be changed in order to customize the experience. 

Options which are available in this tab are divided into three major sections: General, Task Types and Task Hierarchy (automated WBS).

General

In this section you can enable two following options:

Remove tasks not in filter

It defines which issues will be synchronized between Jira and your app. Please note that 'Remove tasks not in filter' feature is set to 'ON' by default. When this option is selected, all tasks which do not fit the current filtering scheme of the Program's Scope, will be removed from the list of tasks (eg. visible on the Gantt module). 

If this option is set to 'OFF', once a Task is modified that it does not fit within the Program's scope, it will remain in the scope of the Program. On the other hand, once it is set back to 'ON' and the app is Re-Synced, it will automatically remove all tasks which do not fit anymore and add new tasks that now fit the filtering scheme (if any were added or redefined).

Recalculate Parents

When selected, this option will automatically update the duration of the parent tasks to resemble the total duration as their children tasks. This means that it won't be possible to change the duration of the parent task on the Gantt chart manually. 



When switched 'OFF', it is again possible to modify their duration and the red-dotted line would indicate the position and duration of the parent task after it is recalculated.

Task Types

Task Types section allows users to define what additional elements (e.g. Versions, Components, Projects) should be added to the scope of the Program and be constantly synchronized in your Work Breakdown Structure. 

As a consequence, they are represented as tasks in the app e.g. on the Gantt module. They can serve you as grouping elements in your Work Breakdown Structure to e.g. present aggregated data and to guard periods of the child tasks.

Such elements are called additional tasks in the app.

Task Hierarchy (automated WBS)

Task Hierarchy or WBS (Work Breakdown Structure) section allows for defining how to automatically build the structure of the tasks within a particular Program. 

You can set the suitable rules by activating respective synchronizers. Simply, click on the synchronizer to activate it.

Note

Remember that activating a given synchronizer (e.g. Project synchronizer) without selecting a corresponding task type ("Synchronize JIRA projects" in this case) is insufficient.

You need to select e.g. "Synchronize JIRA projects" in the Task type section to allow the app to add a proper task to the scope of the Program and synchronize its child tasks later on.


Please note that you configure only the task structure in this section of the app. Dependencies between Tasks (Start-to-End, End-to-Start etc.) are available in the App’s Global Configuration, in the Link configuration page. Make sure to apply all the changes by clicking the 'Save and Sync' button at the very bottom of the page.

Synchronizers - basic rules

The following rules related to automatically built WBS based on active synchronizers were released for Jira Server (BigPicture 7.1.4, BigGantt 3.14.5) and  for Jira Cloud (BigPicture, BigGantt)

The order of the active synchronizers specifies:

  1. the sequence of the performed executed "parent finding" loops executed by the app for every task in the scope of the Program 
    1. e.g: try to find Project parent task → then try to find Version parent task →then try to find Epic parent task etc.
  2. the business priority of the synchronizers
    1. eg. if the order of the synchronizers is as follows: Project → Version → Epic, a system assumes that a Version synchronizer is more important then an Epic synchronizer

Please note that the order of the active synchronizers is important for the final result of the automatically built WBS.

Automated WBS building - how does the algorithm work?

When a full-sync is executed, the following steps regarding WBS building are taken:

  1. A system adds all additional tasks (all tasks that are not Jira issues, but they are included in the scope based on selected Task types in Synchronization tab: Projects, Components, Versions, Agile Backlogs, Agile Sprints) to have all tasks in the scope (and as a consequence: all potential parent tasks in the scope)
  2. A system executes two following loops to build a proper WBS: 
    1. a loop for all active synchronizers
    2. a loop for all tasks in the scope
  3. It means that: 
    1. At first, a system tries to find a parent task for every task consecutively based on the first active synchronizer
    2. Then it tries to find a parent task again for every task consecutively based on the second active synchronizer etc.until all active synchronizers are verified.
  4. The following rules are applied by finding a parent task for a given task within a consecutive synchronizer: 
    1. a system always respects an already built structure by indenting a task (if an indent of the task would be contradictory to its current parent tasks, then an indent is not executed so that a synchronizer never overwrites the current WBS)
    2. an indented task is always moved with all its child tasks.

Please note, that the final result of the automatically built WBS based on the active synchronizers can be different depending on the current structure at the moment of the full-sync.

If you want to reorganize your Work Breakdown Structure entirely after it was already built, we recommend you:

  1. turn off all synchronizers
  2. select "reset Work Breakdown Structure" option
  3. click on "Save and sync".

After taking those steps, your scope will be flattened. Activate the new synchronizers then to build a respective task hierarchy again.

WBS reset

To flatter the WBS disable all of the synchronizers and check the reset option:

Illustrative example

Input data

#1 Tasks in the scope:

Task

Jira project

Fix Versions

Epic link

Project Ana.na.na.
Version 1.0Ana.na.
Version 2.0Ana.na.
Epic-1A-na.
Epic-2A1.0na.
Story-1A1.0Epic-1
Story-2A-Epic-1
Story-3A-Epic-2
Story-4A1.0Epic-2
Story-5A2.0Epic-2

#2 Active synchronizers:

  1. Project
  2. Version
  3. Epic

#3 The list of the tasks at the beginning of the WBS building is flat (no parent tasks).

Output data (automatically built WBS):

1st level

2nd level

3rd level

4th level

Explanation of the task position in a WBS

Project A


the task does not have a parent resulting from active synchronizers


Version 1.0

the parent is Project A, as:

  • "Synchronize project structure" condition is met


Epic-2

the parent is Version 1.0, as:

  • "Synchronize project structure" condition is met
  • "Synchronize version structure" condition is met



Story-3

The parent is Epic-2, as:

  • "Synchronize project structure" condition is met
  • "Synchronize epics" condition is met
  • "Synchronize version structure" condition is not applicable (Epic1 does not have a version specified)



Story-4

The parent is Epic-2, as:

  • "Synchronize project structure" condition is met
  • "Synchronize epics" condition is met
  • "Synchronize version structure" condition is met


Story-1


The parent is Version 1.0, as:

  • "Synchronize project structure" condition is met
  • "Synchronize version structure" condition is met
  • "Synchronize epics" condition is ignored ie. version synchronizer has a higher priority and synchronizing Epic would cause a conflict (Epic-1 is not included in Version 1.0)

Version 2.0

The parent is Project A, as:

  • "Synchronize project structure" condition is met


Story-5

The parent is Version 2.0, as:

  • "Synchronize project structure" condition is met
  • "Synchronize version structure" condition is met
  • "Synchronize epics" condition is ignored ie. version synchronizer has a higher priority and synchronizing Epic would cause a conflict (Epic-1 is not included in Version 2.0)

Epic-1

The parent is Project A, as:

  • "Synchronize project structure" condition is met
  • "Synchronize version structure" condition is not applicable (Epic-1 does not have any version specified)


Story-2


The parent is Project A, as:

  • "Synchronize project structure" condition is met
  • "Synchronize version structure" condition is not applicable (Epic-1 does not have any version specified)
  • "Synchronize epics" condition is met



HIGHLIGHTS