Content
View differences
Updated by Niels Lindenthal almost 5 years ago
# Problem
* It is currently hard to create project schedules as when work packages span a weekend. In these cases the weekend days are counted as normal working days.
* When projects change the start day of a work package the calculation of the finish date does not take into account any non-working days between the start and the finish date.
> **Example:** A task starts on Monday and finishs on Friday. If the task is delayed by one day the finish date is set for the Saturday. Since Saturday is a non-working day in this scenario the more accurate calculation for the finish date would be Monday.
# Solution
* For each each installation an Admin can set a default working-day calendar which is preset for all projects.
* The calculation of the dates takes the work schedule into account (see example in the problem statement).
* Changing the work schedule triggers a rescheduling of current and future work packages.
* Warning
* Background job
* The work schedule is visualized in the front-end in the following views:
* Prio 1: date picker
* Prio 2: Gantt
* Prio 3: Calendar
## Visuals
<figure class="image op-uc-figure" style="width:72.77%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/20674/content"></div></figure>
# Open
* Danger Zone for changing the work schedule. Changing the work schedule will impact your schedule.
# **Out of Scope for the MVC**
* Adding public holidays to the seed data.
* Selecting non-working days on a project level.
* Non-working-days of individual team members.
* Subscribe to external calendars, e.g. Google calendars.
* ##31992
* Informing about non working days when scheduling a meeting
* It is currently hard to create project schedules as when work packages span a weekend. In these cases the weekend days are counted as normal working days.
* When projects change the start day of a work package the calculation of the finish date does not take into account any non-working days between the start and the finish date.
> **Example:** A task starts on Monday and finishs on Friday. If the task is delayed by one day the finish date is set for the Saturday. Since Saturday is a non-working day in this scenario the more accurate calculation for the finish date would be Monday.
# Solution
* For each each installation an Admin can set a default working-day calendar which is preset for all projects.
* The calculation of the dates takes the work schedule into account (see example in the problem statement).
* Changing the work schedule triggers a rescheduling of current and future work packages.
* Warning
* Background job
* The work schedule is visualized in the front-end in the following views:
* Prio 1: date picker
* Prio 2: Gantt
* Prio 3: Calendar
## Visuals
<figure class="image op-uc-figure" style="width:72.77%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/20674/content"></div></figure>
# Open
* Danger Zone for changing the work schedule. Changing the work schedule will impact your schedule.
# **Out of Scope for the MVC**
* Adding public holidays to the seed data.
* Selecting non-working days on a project level.
* Non-working-days of individual team members.
* Subscribe to external calendars, e.g. Google calendars.
* ##31992
* Informing about non working days when scheduling a meeting