Search

Categories
 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

 BigPicture Enterprise
 Jira Cloud

 Jira Server

 BigGantt
 Jira Cloud

 Jira Server

 BigTemplate
 Jira Cloud

 Jira Server

Knowledge Base

Tutorials and tips

Trust Center

BigPicture 8 is here!

Discover the landmark edition of the Atlassian Marketplace top-selling app! The new version is available to all Server and Data Center users. The release for Cloud will follow soon. Visit BigPicture 8 Documentation to learn more about it.

Precise alignment

Task's period will align exactly with the box's period. The fields mapped as start and end dates will get updated to match the boxes start and end dates when a task is planned in one of the time boxes.

This setting is recommended for agile and non agile teams who want to use BigPicture as a Roadmap tool and present their plans using the Gantt module.

The task can be aligned with the time box defined using the Overview- Views - Hierarchy.

Please note, that this sync mechanism is:

  • unidirectional: planning tasks in using Boxes (Program Increments or Iteration) updates the tasks' to fit within the Boxes' duration. However, updating the tasks' date estimates does not add a task to the Box.
  • single-shot operation: a task period is always updated once the task is planned for a Box (e.g. using Board module), but if you adjust the task's period once it is planned for a box (e.g. on the Gantt module) the app will not validate the adjustment even if the new period would not fit the Box's period.

The above-mentioned update of the task period will be executed properly only if all task scheduling rules (parent-child relation, task mode, inward dependency, etc.) allow executing the operation. E.g. if a Story has a parent task in the task structure that has a "lock" mode set, the app may not update the Story period if it exceeds the parent period after the update. 

Please note, that once a task period is rescheduled, it may trigger a rescheduling of related tasks (linked tasks or parent/children in the task structure).


Go back to Program Box Configuration - Tasks - Scheduling.