Non-working days
- Anna Ciepłota
- Magdalena Żaczek
- Marta Golab (Deactivated)
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: