Support for Atlassian Server Products (and apps like BigPicture) has ended in February 2024.
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 support@appfire.com
Non-working days
Introduction
The App can recognize 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).
The Workload plan restriction will not be applied to parent tasks in auto bottom-up modes. When the child task has a different assignee, and its start/end date influences the parent's duration, the parent's start/end date will be set according to the child's date, even if it's planned on a non-working day for the parent task's assignee. Simply put: parent always ignores schedules, i.e., You can set start and end date on non-working days if children's dates are set up on such days.
If working days are changed (either globally or for a resource), it has no effect on the scheduling of existing tasks. An action (such as a change of task duration) will trigger a new validation - the validation mechanism will take all non-working days into account and move tasks accordingly.
Otherwise, some changes (e.g., adding a long absence or changing global working days) could have a massive unintended impact on the scheduling.
Displaying non-working days on the timeline
The non-working days are displayed on the timeline of the Gantt and Resources modules as grey cells. By default, only the weekend is marked as non-working:
Calculating tasks period based on assignee's working days
Please note that calculating the task period based on the assignee's working days does not apply to parent tasks in the WBS structure. The reason for this limitation is that parent tasks can be automatically recalculated based on their children's tasks which may be in contradiction with the working days of a resource assigned to the task.
You can display the non-working days of an individual assignee using the Gantt module's Resources panel but also on the timeline when the Resources panel is not enabled. Click on one of the tasks which are already assigned to grey out the non-working days.
You can enable the 'Calculate tasks automatically based on assignee's working days' option in the App's Configuration (you need to be a Jira administrator to access this page) to show non-working days when you click on a task and allow the scheduling mechanism to reschedule your task taking into account the non-working days.
The scheduling mechanism performs the following:
checks assignee's working days (individual resource) that allow the assignee to complete the task based on:
resource's Holiday, Workload and Absence plans,
task start date,
task duration.
calculates the start date of the task, and in case a task's start date is a non-working day, the task will be updated to start on the earliest possible working day that comes after the task's start date.
calculates the end date of the task and checks consecutively the assignee's working days that fit task duration until the task can be fully completed.
If it is not possible to determine a correct task period because the assignee has no working days in the future, the task will not be rescheduled. In that case, the task will be marked with a red frame if warnings are enabled.
When you change the task's assignee, it might cause automatic rescheduling of the task. This will take place if the new assignee's schedule is different from the previous one. The only exception to this rule is when a task is in the Locked mode - as its position will not be recalculated.