The actual or planned workload of the individual resources or a Team. The effort expressed as the time or number of Story Points required to complete a task is evenly distributed over the task's duration.


To assess the performance of your project over time, you can set Baselines and track deviations from your initial schedule. 

The Baselines can be synchronized with Jira (Tasks requires Jira Admin permissions) and the synced fields can be added to Column views or as fields to the Task / Risk Cards.

You can create and delete Baselines for all the tasks in the scope of the Box or for selected tasks only. They are displayed as bold lines, showing the position of the task at the moment of creating the Baseline.

Basic task

Basic tasks are tasks stored by the App and are not synchronized with Jira or other connected tools like Trello. Basic tasks can be viewed only using the App's Gantt, Scope, Board modules or the WBS Widget.

They can coexist with other tasks and work great as placeholders or temporary tasks and simulate higher levels in the hierarchy or serve as additional information box. The App uses them to replace non-issue Jira entities (like Components, Versions, Projects) which it is unable to recreate in Jira while cloning the scope.

Box hierarchy 

A tree structure consisting of a Box root (parent node) and Boxes (nodes). Each node can potentially have a different type - Box type,  and additional sub-Boxes.

The hierarchy is presented in the Hierarchy and Timeline modes of the Overview module as well as in the Box Switcher.

Box type

Box template which defines most relevant characteristics of a Box (node), such as:

  • types of parent boxes to which it can be added,
  • default module configuration and names
  • default column view of different modules
  • default card layout
  • default task mode
  • default period mode

Box types can be defined by BigPictures administrators. Read more here.

Box module

The following modules are available in BigGantt:

  • Overview
  • Gantt

The following modules are available in BigPicture:

  • Overview
  • Gantt
  • Risks
  • Roadmap
  • Board
  • Calendar
  • Resources 
  • Teams

Most of the modules can be preconfigured using Box types. Read more here.

Box switcher

The Box switcher is a mini version of the Hierarchy mode of the Overview module. It shows the Box names and the hierachy

Use the Box switcher to easily shift between different Boxes. Once opened, the active Box will be highlighted so you can easily switch to a sub-Box or a different Box.

You will be able to browse Boxes to which you have permissions only.

The Box switcher is displayed in the Apps header for each module and in the WBS Widget and Skill Widget which can be added to the issue screen.

Box status

Box status is displayed next to the Box name in the Box switcher. You can change the Box status in different sections of the app. In the Overview module using the right-click or by drag and drop when in Kanban mode. You can also change the status using the Board module or in the Scope definition tab of the  Box configuration.

The status is indicated using colors and The following color coded statuses are available:

  • Not started - gray
  • In progress - blue
  • Done - green

Column views

Column Views allow you to add different fields as columns to the task list and configure their display and aggregation settings which determine how data is presented in the Gantt and Scope type module's task list.


The App can connect different tools to your Jira instance. These include tools like other Jira Cloud instances (coming soon), Trello or MS Azure . The connection field (status) informs you if your instance was already connected.

Context Box

Box which you are currently viewing. The Box name and its status is displayed in the Box Switcher.

Critical path

Critical path
The critical path is the longest sequence of tasks that determines the project duration. This feature highlights all the tasks on the critical path with the red colour. Tasks on the Critical path will also be listed in the Gantt Infobar.

To highlight the entire sequence, you must define dependency links between tasks. Only the strong links that impact scheduling will determine the tasks on the critical path.


Task dependencies
Dependencies specify the relationships between tasks, milestones, and other items which can be presented on the timeline and can be displayed by the Gantt and Board type modules (Gantt and Board are the default module names used). By defining dependencies, you can not only automate task scheduling but also highlight relations between tasks without impacting the schedule. Keep in mind, that the items presented on the Gantt chart are system-wide and changing their dependencies might affect tasks in other Boxes or connected tools.

The Gantt module takes linking to the next level and you can use non-Jira links to define dependencies between Issues and non-issues, such as Projects, Versions, Components, Sprints and Backlog, Checklists, etc. You can visualize up to five different links. Almost any native Jira link or custom link can be synchronized.

The Board module dependencies are color coded so that you can easily find the tasks which need your attention.

The strong dependencies between tasks impact the scheduling of those tasks (does not apply to Soft links). Linked tasks will push and pull each other in time, according to the properties of the dependency between them. Those properties and their impact works as listed below:

  • Dependency type determines the direction of the dependency and also which of the Tasks' dates are relevant. We call them "relevant", because certain changes to those dates might cause either rescheduling of the dependant tasks or can be even impossible to perform (the app will immediately revert them task to the previously calculated dates). To get more information on which are those changes and what is their outcome, see the table at the bottom of this page. Changes of the dates that are not "relevant" do not cause rescheduling of this dependency (but might still cause changes to its parent's or children's periods).
  • Lag Time is the time period calculated in days dividing the inked tasks. Lag time has the highest priority over other Dependency properties. In both ASAP and non-ASAP modes the lag time will be respected and applied regardless of other circumstances. The type of Dependency determines which date (Start or End) of the Source task the Lag Time will be added to.
  • ASAP mode always schedules Target task to take place 'as soon as possible', according to dependency type. This renders the Target task strictly dependant on the Source. Therefore it will be impossible to drag and drop it, neither to the future nor the past. The Target task will always revert to its position previously calculated by scheduling.

Effort mode

The Resources and Gantt module show the resource workload vs capacity in three different effort mods:

  • Original estimate mode - use this mode to show planned workload versus the resource capacity.
  • Remaining estimate mode - use this mode to show workload history (Spent time), and the remaining workload versus the resource capacity.
  • Story points mode - use this mode to show the planned workload versus resource capacity expressed in Story Points.


BigPicture can be integrated with other with external sources of tasks such as Trello and Jira Cloud instance. Any software app (instance?) to which you can connect using BigPicture such as Trello or Jira which is hosted on a different platform than your currently used app.


Gadgets allow you to add dynamic content to a Confluence page or Jira application dashboard. There are three Gadgets to choose from:

  • Boxes - shows the Hierarchy mode of the Overview module.
  • Gantt - shows the tasks as presented by the Gantt module.
  • Risks - shows the Risk matrix of the Risks module.


Gadgets allow you to add dynamic content to a Confluence page or Jira application dashboard. There are two Gadgets to choose from:

  • Boxes - shows the Hierarchy mode of the Overview module.
  • Gantt - shows the tasks as presented by the Gantt module.

Holiday plan

A calendar that is used to reflect the holidays and observances as non-working day which reduce the capacity of Teams or individual Resources (Team members).


BigPicture is an add-on hosted on your Jira instance.

Inheritance mode

When creating a new Box type or moving a sub-Box to a different parent Box, thanks to the Inheritance mode, the Box type configuration can be passed on from the upper-level Box type to the sub-Box type. 

The are three Inheritance modes which determine whether users will be able to customise the Box settings. Inheritance modes can be set for:

  • Card Views,
  • Quick filters
  • Column Views
  • Security


There may be a number of important dates that call for special care and attention. You can highlight them using a marker whatever they may be: from an important external event to a deadline, you name it. Once highlighted, they'll become instantly visible to all users with access to the App and appropriate security roles to view the Box content.

Markers can only be viewed using the App and when you add a marker, it will be visible on the timeline of the following modules:

  • Overview
  • Gantt
  • Board
  • Roadmap

With live synchronization and a variety of colors to choose from, you can make your timeline a complete source of information for everyone.


Used to mark specific points along a project timeline and they do not impact the project duration. When a task is converted to a Milestone, a label can be created #milestone in a filter to show Milestones only.


You can multi-select Boxes or tasks using CRTL+right click (or CMD on Mac). Once selected, the list of tasks will be highlighted in blue. You can, for example, drag-and-drop it them in-between other tasks to move the list.

Alternatively you can move the tasks using the arrows found on the module's header.

A notification will be displayed if the operation was partially successful or unsuccessful.

Multi-select is supported by the following modules:

  • Overview
  • Gantt
  • Scope 
  • Board

Non-working day

Non working days
The App can recognise non-working days and adjust the task period. This means that if you plan a task or part of your task's period on a non-working day it will be moved or extended or shortened.

You can define the non-working days in the Administration section:

Each non-working day reduces the capacity of your Resource. The capacity is calculated by the App and does not sync with the Host platform (you will not be able to see the capacity of your Resource directly in Jira or Trello).

Period warning

Period warnings occur when a parent task can not be recalculated due to a constrain, such as a blocking task (for example a task in Locked mode), non-working day, or when you use the manual task mode. 

The warning is displayed as a yellow box with a dashed-line frame and shows the position of the parent tasks calculated based on its children.

Task Progress

Task progress

Resources panel

Resources panel
The Resources panel lets you preview how much work has been assigned.

With the Resource panel enabled, the workload of each resource (assignee) will be counted in hours and color coded depending on the resource capacity. 

The workload data is filter-sensitive, i.e. only the tasks in the current view are included in the workload calculation. You can use Quick filters or the Search Box to filter out tasks and simulate different scenarios.

As a rule, effort is distributed evenly throughout the duration of a task but you can change how it is distributed in Resources module. To learn more go to Workload contouring.


Any Jira issue with the 'Risk probability' and 'Risk consequence' fields values. ?????

Scope definition

Scope of the Box can be defined using automated and manual rules. 

Search Box
The Search box functionality will help you quickly find the things you're interested in, and filter out unwanted tasks or Boxes. The search box operates in two modes:
    • Text search mode which filters information based on the Jira summary field (Boxes and tasks)
    • JQL mode which, as the name suggests, filters information using JQL queries (tasks only)




The skill are defined at:

  • the task level - skill required to complete a task. The related effort is used to calculate the skill demand and it is evenly distributed over the tasks duration. The skill demand will be display in Resource module's Skill panel.
  • the resource level - skill acquired by the resource. The resource’s time is allocated across different skills. Skills weight most in the "Perfect match algorithm" which is approximately 80%.

Each skill has a start and end date so you can plan the skill development over time.


Any Jira 


Consists of Team members - Jira users. Each member has a membership and you can define the member's availability in each Team.

Team Capacity

The capability to achieve a set amount of productivity within a single day calculated as the sum of Team members' capacities. Team capacity factors in the existing manpower known to readily possess the necessary skill set as well as the number of hours in a work day.

Team code

Team code is used for identifying teams by the App's modules and, when synchronized, also the Host and connected platforms. Depending on the configuration, the Team code is stored as the following fields:

  • Labels type
  • Select list – single choice type
  • --none-- (not synchronized)

You can use these fields in your JQL to create a Jira Board dedicated for a specific team or as Quick Filters.

Team Member

A Jira user with a Team membership.


A period of time defining the duration of the Box with a Start and End date. Time-Boxes can overlap or be sequential. Each Time-Box has a predefined type - Box Type. 


The Timeline is common element of the following modules:

  • Overview - Timeline mode - you can show and edit Boxes using drag and drop.
  • Gantt - you can show Tasks, Projects, Sprints, Backlog, Components, Versions, Boxes and Markers. 
  • Board and Roadmap - you can show Markers and Boxes. 
  • Resource - you can show tasks.


There are two widgets which you can add the Detailed issue view:

Workload plan

A calendar that is used to reflect specific working hours of an individual resource and is the basis for capacity calculation of Teams or individual Resources (Team members).Workload plans are used for defining exact working hours. You can create as many as you like and assign to your resources separately.