Content
View differences
Updated by Christophe Bliard almost 4 years ago
Copied from <mention class="mention" data-id="31992" data-type="work_package" data-text="#31992">#31992</mention> (which is still authoritative, so double check the requirements there)
> ### Change in set of working days (instance admin)
>
> * When an administrator changes non-working days via instance admin settings (adds or removes a working day), this will affect dates of scheduled work packages. If non-working days are added or removed for the instance by an admin, the _duration_ is preserved, which might mean the start and finish dates might change:
> * \[...\]
> * If a work package included a date that is now a non-working day, the finish date moves to the corresponding number of now-excluded days to maintain duration.
> * If a work package was scheduled to start on a date it is now a non-working day, the start date moves to the earliest working day in the future (and the finish date changes by consequence).
> * Even if a work package does not span or included a day that is now a non-working day, it might nevertheless be affected because of relations.
> * Eg. A preceding work package has pushed its dates forwards or backwards such that it now spans a non-working day. In this case, the work package will be pushed/pulled as it does today, and the work package will be rescheduled as any other work package (it adapt it start and finish dates to maintain duration).
> * \[...\]
Journal updates are handled in The journal will be displayed to the implementation user for _affected_ work package <mention class="mention" data-id="43640" data-type="work_package" data-text="#43640">#43640</mention>. packages only, attributed to the author (admin who make the change), like so:
> * For changes to the work week:
> * "_**Working days** changed (Friday is now non-working) by Jean-Cérien_"
> * "_**Start date** changed from {old date} to {new date}_"
> * "_**Finish date** changed from {old date} to {new date}_"
> ### Change in set of working days (instance admin)
>
> * When an administrator changes non-working days via instance admin settings (adds or removes a working day), this will affect dates of scheduled work packages. If non-working days are added or removed for the instance by an admin, the _duration_ is preserved, which might mean the start and finish dates might change:
> * \[...\]
> * If a work package included a date that is now a non-working day, the finish date moves to the corresponding number of now-excluded days to maintain duration.
> * If a work package was scheduled to start on a date it is now a non-working day, the start date moves to the earliest working day in the future (and the finish date changes by consequence).
> * Even if a work package does not span or included a day that is now a non-working day, it might nevertheless be affected because of relations.
> * Eg. A preceding work package has pushed its dates forwards or backwards such that it now spans a non-working day. In this case, the work package will be pushed/pulled as it does today, and the work package will be rescheduled as any other work package (it adapt it start and finish dates to maintain duration).
> * \[...\]
Journal updates are handled in
> * For changes to the work week:
> * "_**Working days** changed (Friday is now non-working) by Jean-Cérien_"
> * "_**Start date** changed from {old date} to {new date}_"
> * "_**Finish date** changed from {old date} to {new date}_"