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.

Smart alignment

Task's period will align to the start or end date of the Box without changing the tasks duration (if possible). The fields mapped as start and end dates will get updated, when a task is planned in one of the Boxes, such that the task will start on the start date of the Box (when moved to a future Box) or end on the end date of the Box (if moved to a previous Box).

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

The task can be aligned with the Time-box created using the Overview- Views - Hierarchy.

Before vs after adjustment

The tasks before the adjustment are shown on the left-hand side of the above image and the adjustment outcome is show on the right-hand side.

All tasks were added to Sprint2 (the Iteration name was renamed to Sprint) using the Board module.

1) Purple task - Whole task period is contained in the iteration period →  do nothing.

2) Navy blue task - Whole task period precedes the iteration period (Task period is not longer than an iteration period) →  task will be moved to start at the beginning of the iteration and the period length will remain unchanged.

3) Red task - Whole task period is later than the iteration period (Task period is not longer than iteration period) →  task will be moved to end at the end of the iteration, period length will remain unchanged.

4) Orange task - Whole task period precedes the iteration period (Task period is longer than the iteration period) →  task will be moved to start at the beginning of the iteration and end at the end of the iteration.

5) Light green task - Whole task period is later than the iteration period (Task period which is longer than iteration period) →  task will be moved to start at the beginning of the iteration and end at the end of the iteration.

6) Grey task - Whole iteration period is contained within the task period →  task will be fitted in, meaning it will be moved to start at the beginning of the iteration and to end at the end of the iteration.

7) Dark green - Part of task period precedes the iteration period and part of it overlaps iteration period. (Task period is not longer than the iteration period) →  the task will be moved to start at the beginning of the iteration, and the period length will remain unchanged.

8) Brown task - Part of the task period overlaps iteration period, part is after (Task period is not longer than the iteration period) →  task will be moved to end at the end of the iteration, period length will remain unchanged.

9) Turquoise task - Part of a task period overlaps iteration period, and part of it is outside of the iteration (Task period is longer than iteration period) →  task will be fitted in, meaning it will be moved to start at the beginning of the iteration and end at the end of the iteration.

10) Black task - Part of a task period overlaps iteration period, and a part of it is located outside (Task period is longer than the iteration period) →  task will be moved to start at the beginning of the iteration and end at the end of the iteration.

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.