Are you planning a migration to Cloud? Make sure you don't lose your BigPicture data/configurations in the process. Check out this page for information on how to migrate BigPicture's data to Cloud. If you have any questions please email firstname.lastname@example.org
BigPicture provides a number of automation mechanisms that help you save time and keep hundreds of tasks under control and within deadlines.
You can find a list of solutions below.
A task in multiple boxes
If you make changes to a task that is in multiple boxes, changes are automatically implemented in other boxes. When each box is configured differently, the resulting task's period is 'evenly shaped' by the rules of each box. The task's position and duration on the timeline remain the same in all of the boxes.
BigPicture automatically updates fields in Jira (or another platform) once you edit a task or create a dependency. Changes to tasks can be made also by automation based on modifications to the task position in the task structure.
If you move a task to an appropriate place in the task structure, BigPicture can automatically perform the following actions:
Assign a task to the correct sprint, version, or epic.
Unlink a task from the correct sprint, version, or epic.
According to multiple rules, the auto-scheduling function aims to calculate the task's period (start and end dates). Those rules are applied simultaneously, but each has its own priority. Depending on the implemented rules, you can end up with different setups of scheduling functions for each task.
The table below lists the rules according to the following priority:
Dependencies are relationships between tasks, milestones, and other items. The mechanism can simultaneously move one or more tasks linked to a task that is being moved. By defining dependencies, task dates, and other initiatives are updated automatically as a result of changes made to a project.
You are also free to define dependencies between initiatives such as versions or projects.
If you do NOT want dependencies to affect tasks, you can disable automation by setting an appropriate scheduling mode.
You can mark days in the calendar as non-working days by setting schedules or assigning a day off to an employee. BigPicture recognizes non-working days and adjusts a task period accordingly. 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.
Another solution that helps you manage and monitor tasks more easily is the possibility to automatically calculate task dates based on estimates or the time logged on tasks.
Activating the mechanism modifies the way of editing the “Start Date” field. Entering a new “Start Date” results in moving a task. The duration of a task is NOT changed, and its “Original Estimate” remains unchanged.
Automatic calculation of task dates based on estimates proves useful when:
The “Original Estimate” field contains estimates for a task. If you enter the “Start Date”, the “End Date” is calculated automatically based on an estimate.
You monitor the project estimate based on the sum of the “Original Estimate” for all tasks in that project. If you update task dates, task estimates along with the final project estimate are updated automatically.
You want task dates to be adjusted to the time logged on a task. As a result, you can track in real-time how tasks match the dates to the actual progress of work logged by other employees.
BigPicture offers the possibility to automatically align task dates with iteration dates. With such a solution, you can see a visualization of tasks in the Gantt module, or it is possible to automatically set expected end dates for tasks (e.g., bug type) that are assigned to a given sprint.