Content
Updated by Christophe Bliard about 11 hours ago
**As a** project manager
**I want to** automatically move a set of work packages to the earliest date possible
**So that** I don't have to do this manually.
# Visuals #### Acceptance criteria
_**Note:** Please check_ [_Figma_](https://www.figma.com/design/HrWVktq0SsGI2dqqIKQ11M/Scheduling---Lag-and-Modes?node-id=175-3641) _for ##### General
* There are only two scheduling modes.
* **Manual**: The user can freely set the most recent mockups._ start and finish dates, but relations are ignored.
* **Automatic:** Automatically sets the start date based on a predecessor. The user can only set duration.
* This mode is also used for parents, where the duration field is also inactive.
* Any time a user wants to manually choose dates for a work package, they select manual scheduling.
* By default, all new work packages will be manually scheduled.
* A new manually-scheduled work package will either have no dates, or take the current date (depending on existing settings).
* Every newly created work package will have no predecessor; they have to be added later.
* If it's a new child work package, it will continue behaving as it does today and by default take the parent's start date.
* For automatic scheduling, a predecessor is required. If there are no predecessors:
* the top banner will show an error informing the user that a predecessor is required
* all fields will be disabled (non-working days, save action..)
* we will display a blankslate with a primary action to add a predecessor (permissions allowing)
* If a work package was previously manually scheduled, but is then added as a successor. Or if a predecessor is added to a manually scheduled work package:
* We will give the user a confirmation dialog with two options (see mockups for text):
* Maintain manual scheduling
* Switch to automatic
**Parent/children relations**
* Parents will continue to behave as it does today, except they will now be in Automatic mode.
* They "cover" the date ranges of the two children and children can have an indirect link to relationships of the parents.
* Their dates will not be editable.
* They can be switched to manual mode.
* Adding a child to a manually-scheduled work package will automatically move the parent to automatic mode.
* If the parent previously had dates, those will be overwritten by those of the children.
* If the child does not yet have dates, neither will the parent. Previous dates (before being a parent) are lost, as is the case today.
* Removing the last child of a parent will switch the now non-parent work package mode to model, whilst preserving dates before the removal of the last child.
* If neither the child nor the parent had dates, it will simply be switched to manual mode without any dates.
**Connection to stages and gates**
* It might take some time to develop project start date and also the association for work packages to stages. This work package will be independent of that feature, described separately: ##58421
##### Gantt view
* You can freely move manually scheduled work packages.
* If you try to move an automatically scheduled successor with lag, ask if user wants to (see mockups for text):
* Change lag (reduce or extend)
* Keep relation and switch to manual
* Delete relation and switch to manual
* For work packages without any predecessors, it will not be possible to select Automatic mode.
* Clicking on "Automatic" will show a blankslate with no actions possible.
* If the dates of a predecessor of an automatically scheduled work package are removed, the successor will go into manual mode. But we need to ask the user for confirmation:
* "This work package has at least one automatically scheduled successor. Removing the dates here will switch the successor to manual scheduling to preserve its dates."
* If all predecessors of an automatically scheduled work package are deleted:
* The "successor" goes into manual mode. We will ask for user confirmation:
* "This work package has at least one automatically scheduled successor. Deleting this work package will switch the successor to manual scheduling to preserve its dates."
* The relation is deleted
##### **Migration from an earlier version**
* Dates will **NOT** change automatically. All existing dates are preserved.
* For work packages with no predecessors (or with no relations at all), they will be switched to manual scheduling.
* These work packages are switched to manual scheduling regardless of having dates or not.
* When relations exist,
* If there was a gap in a predecessor/successor relationship, the successor will be set to “Automatic" with a lag set for the relation with the closest predecessor (the one that finishes latest).
* In a multi-relationship situation, earlier predecessors that do not affect the date of the successor do not have lag added.
* If the relation exists but there are no dates, they will be switched to manual scheduling mode.
* If the relationship is parent-child, there are no changes to dates; the parent remains in automatic mode (as is the case now) and the children follow the rules above.
* Manually scheduled work packages remain so.
##### **Date picker**
* The date picker will be Primerised.
* There is now an _UnderlineNav_ bar at the top:
* With three options:
* Dates
* Predecessors
* Successors
* Children
* There is a new segmented control with label "Scheduling mode"
* There is a help icon next to the label. On hover, it displays a tooltip with this text: "‘Manual’ lets you pick fixed dates freely but ignores all predecessors. ‘Automatic’ selects the earliest possible start date for this work package, which cannot be modified."
* Options: "Manual" and "Automatic"
* The "Working days only" toggle becomes a checkbox aligned to the far right edge of the same line as the segmented control.
* In **Manual** mode:
* The dates are freely selectable, without restrictions.
* Relations don't affect the start and finish dates.
* A manually scheduled work package can push and pull successors that are automatically scheduled
* A manual work package can start before any of their predecessors
* A manually scheduled work package will not push a predecessor to the past when it's moved to the past
* In **Automatic** mode:
* The _Start date_ and _Finish date_ fields are read-only
* The "Today" links under the date fields are disabled  (but not removed so that elements in the date picker don't move when changing modes)
* Duration remains editable
* The mini calendar goes into read-only mode
##### **Date picker: Predecessor, Successor and Children tabs**
* Each of the tabs displays the number of relations of that type with a badge
* In each tab, all relations of that type are displayed in a box list
* The content is the same as in the "Relations" tab of the work package, but without the section header
* In the "Predecessors" tab, when there are multiple predecessors, the one setting the date of the current work package has a label that says "Closest" next to the date and lag information
* \[open\]\[cbl\] When two predecessors or more have the same end date, do we show "Main" for all of them, or for only one? If only one, how is it choosen? (must be deterministic)
##### **Date picker banners:**
**Manual scheduling:**
* Colour: Warning orange
* Action: Show relations
* Case 1: Relations exist but no predecessors.
* **Manually scheduled. Dates not affected by relations.**
Click on “Show relations” for Gantt overview
* Case 2: There are predecessors but a gap of over two days with the finish date of the latest predecessor.
* **Manually scheduled. Dates not affected by relations.**
There is a gap between this and all predecessors.
* Case 3: There are predecessors and the current work package overlaps with at least one of them.
* **Manually scheduled. Dates not affected by relations.**
Overlaps with at least one predecessor.
* Case 4: Work package has children.
* **Manually scheduled. Dates not affected by relations.**
This has child work package but their start dates are ignored.
**Automatic:**
* Colour: Info blue
* Action: Show relations
* Case 1: There is a predecessor.
* **The start date is set by a predecessor.**
Click on “Show relations” for Gantt overview.
* Case 4: The work package is a parent.
* **The dates are determined by child work packages.**
Click on “Show relations” for Gantt overview.
* If a work package is both a parent and has predecessors, this "parent" message will be displayed.
# Features Delivery
The To deliver value often, the development is split into in the following features: chunks:
## ##59539
workPackageValue:59539:status | workPackageValue:59539:version
workPackageValue:59539:description
## ##59540
workPackageValue:59540:status | workPackageValue:59540:version
workPackageValue:59540:description
## ##59541
workPackageValue:59541:status | workPackageValue:59541:version
workPackageValue:59541:description
## ##59542
workPackageValue:59542:status | workPackageValue:59542:version
workPackageValue:59542:description
## ##59731
workPackageValue:59731:status | workPackageValue:59731:version
workPackageValue:59731:description
# #### Out of scope
* Other scheduling modes and constraints such as "Must start on" or "Start not later than", "Start no earlier than".
* Editable lag in relations tab.
* This will have been addressed by the time we work on this feature: ###22360
#### Visuals
_**Note:** Please check_ [_Figma_](https://www.figma.com/design/HrWVktq0SsGI2dqqIKQ11M/Scheduling---Lag-and-Modes?node-id=175-3641) _for the most recent mockups._
**Manual scheduling (but predecessors overlap):**
<img class="image_resized op-uc-image op-uc-image_inline" style="width:540px;" src="/api/v3/attachments/226779/content">
**As soon as possible (start date set by predecessors):**
<img class="image_resized op-uc-image op-uc-image_inline" style="width:540px;" src="/api/v3/attachments/226780/content">
**Date picker Predecessors tab:**
<img class="image_resized op-uc-image op-uc-image_inline" style="width:540px;" src="/api/v3/attachments/226781/content">
**Options when trying to move an automatically scheduled work package in Gantt view:**
<img class="image_resized op-uc-image op-uc-image_inline" style="width:540px;" src="/api/v3/attachments/226787/content">
**Options when adding a predecessor to a manually scheduled work package in Gantt view:**
<img class="image_resized op-uc-image op-uc-image_inline" style="width:540px;" src="/api/v3/attachments/226792/content">
**I want to** automatically move a set of work packages to the earliest date possible
**So that** I don't have to do this manually.
# Visuals
_**Note:** Please check_ [_Figma_](https://www.figma.com/design/HrWVktq0SsGI2dqqIKQ11M/Scheduling---Lag-and-Modes?node-id=175-3641) _for
* There are only two scheduling modes.
* **Manual**: The user can freely set
* **Automatic:** Automatically sets the start date based on a predecessor. The user can only set duration.
* This mode is also used for parents, where the duration field is also inactive.
* Any time a user wants to manually choose dates for a work package, they select manual scheduling.
* By default, all new work packages will be manually scheduled.
* A new manually-scheduled work package will either have no dates, or take the current date (depending on existing settings).
* Every newly created work package will have no predecessor; they have to be added later.
* If it&#39;s a new child work package, it will continue behaving as it does today and by default take the parent&#39;s start date.
* For automatic scheduling, a predecessor is required. If there are no predecessors:
* the top banner will show an error informing the user that a predecessor is required
* all fields will be disabled (non-working days, save action..)
* we will display a blankslate with a primary action to add a predecessor (permissions allowing)
* If a work package was previously manually scheduled, but is then added as a successor. Or if a predecessor is added to a manually scheduled work package:
* We will give the user a confirmation dialog with two options (see mockups for text):
* Maintain manual scheduling
* Switch to automatic
**Parent/children relations**
* They &quot;cover&quot; the date ranges of the two children and children can have an indirect link to relationships of the parents.
* Their dates will not be editable.
* They can be switched to manual mode.
* Adding a child to a manually-scheduled work package will automatically move the parent to automatic mode.
* If the parent previously had dates, those will be overwritten by those of the children.
* If the child does not yet have dates, neither will the parent. Previous dates (before being a parent) are lost, as is the case today.
* Removing the last child of a parent will switch the now non-parent work package mode to model, whilst preserving dates before the removal of the last child.
* If neither the child nor the parent had dates, it will simply be switched to manual mode without any dates.
**Connection to stages and gates**
* It might take some time to develop project start date and also the association for work packages to stages. This work package will be independent of that feature, described separately: ##58421
##### Gantt view
* You can freely move manually scheduled work packages.
* If you try to move an automatically scheduled successor with lag, ask if user wants to (see mockups for text):
* Change lag (reduce or extend)
* Keep relation and switch to manual
* Delete relation and switch to manual
* For work packages without any predecessors, it will not be possible to select Automatic mode.
* Clicking on &quot;Automatic&quot; will show a blankslate with no actions possible.
* If the dates of a predecessor of an automatically scheduled work package are removed, the successor will go into manual mode. But we need to ask the user for confirmation:
* &quot;This work package has at least one automatically scheduled successor. Removing the dates here will switch the successor to manual scheduling to preserve its dates.&quot;
* If all predecessors of an automatically scheduled work package are deleted:
* The &quot;successor&quot; goes into manual mode. We will ask for user confirmation:
* &quot;This work package has at least one automatically scheduled successor. Deleting this work package will switch the successor to manual scheduling to preserve its dates.&quot;
* The relation is deleted
##### **Migration from an earlier version**
* Dates will **NOT** change automatically. All existing dates are preserved.
* For work packages with no predecessors (or with no relations at all), they will be switched to manual scheduling.
* These work packages are switched to manual scheduling regardless of having dates or not.
* When relations exist,
* If there was a gap in a predecessor/successor relationship, the successor will be set to “Automatic&quot; with a lag set for the relation with the closest predecessor (the one that finishes latest).
* In a multi-relationship situation, earlier predecessors that do not affect the date of the successor do not have lag added.
* If the relation exists but there are no dates, they will be switched to manual scheduling mode.
* If the relationship is parent-child, there are no changes to dates; the parent remains in automatic mode (as is the case now) and the children follow the rules above.
* Manually scheduled work packages remain so.
##### **Date picker**
* The date picker will be Primerised.
* There is now an _UnderlineNav_ bar at the top:
* With three options:
* Dates
* Predecessors
* Successors
* Children
* There is a new segmented control with label &quot;Scheduling mode&quot;
* There is a help icon next to the label. On hover, it displays a tooltip with this text: &quot;‘Manual’ lets you pick fixed dates freely but ignores all predecessors. ‘Automatic’ selects the earliest possible start date for this work package, which cannot be modified.&quot;
* Options: &quot;Manual&quot; and &quot;Automatic&quot;
* The &quot;Working days only&quot; toggle becomes a checkbox aligned to the far right edge of the same line as the segmented control.
* In **Manual** mode:
* The dates are freely selectable, without restrictions.
* Relations don&#39;t affect the start and finish dates.
* A manually scheduled work package can push and pull successors that are automatically scheduled
* A manual work package can start before any of their predecessors
* A manually scheduled work package will not push a predecessor to the past when it&#39;s moved to the past
* In **Automatic** mode:
* The _Start date_ and _Finish date_ fields are read-only
* The &quot;Today&quot; links under the date fields are disabled &nbsp;(but not removed so that elements in the date picker don&#39;t move when changing modes)
* Duration remains editable
* The mini calendar goes into read-only mode
##### **Date picker: Predecessor, Successor and Children tabs**
* Each of the tabs displays the number of relations of that type with a badge
* In each tab, all relations of that type are displayed in a box list
* The content is the same as in the &quot;Relations&quot; tab of the work package, but without the section header
* In the &quot;Predecessors&quot; tab, when there are multiple predecessors, the one setting the date of the current work package has a label that says &quot;Closest&quot; next to the date and lag information
* \[open\]\[cbl\] When two predecessors or more have the same end date, do we show &quot;Main&quot; for all of them, or for only one? If only one, how is it choosen? (must be deterministic)
##### **Date picker banners:**
**Manual scheduling:**
* Colour: Warning orange
* Action: Show relations
* Case 1: Relations exist but no predecessors.
* **Manually scheduled. Dates not affected by relations.**
Click on “Show relations” for Gantt overview
* Case 2: There are predecessors but a gap of over two days with the finish date of the latest predecessor.
* **Manually scheduled. Dates not affected by relations.**
There is a gap between this and all predecessors.
* Case 3: There are predecessors and the current work package overlaps with at least one of them.
* **Manually scheduled. Dates not affected by relations.**
Overlaps with at least one predecessor.
* Case 4: Work package has children.
* **Manually scheduled. Dates not affected by relations.**
This has child work package but their start dates are ignored.
**Automatic:**
* Colour: Info blue
* Action: Show relations
* Case 1: There is a predecessor.
* **The start date is set by a predecessor.**
Click on “Show relations” for Gantt overview.
* Case 4: The work package is a parent.
* **The dates are determined by child work packages.**
Click on “Show relations” for Gantt overview.
* If a work package is both a parent and has predecessors, this &quot;parent&quot; message will be displayed.
The
## ##59539
workPackageValue:59539:status | workPackageValue:59539:version
workPackageValue:59539:description
## ##59540
workPackageValue:59540:status | workPackageValue:59540:version
workPackageValue:59540:description
## ##59541
workPackageValue:59541:status | workPackageValue:59541:version
workPackageValue:59541:description
## ##59542
workPackageValue:59542:status | workPackageValue:59542:version
workPackageValue:59542:description
## ##59731
workPackageValue:59731:status | workPackageValue:59731:version
workPackageValue:59731:description
#
* Other scheduling modes and constraints such as "Must start on" or "Start not later than", "Start no earlier than".
* Editable lag in relations tab.
* This will have been addressed by the time we work on this feature: ###22360
#### Visuals
_**Note:** Please check_ [_Figma_](https://www.figma.com/design/HrWVktq0SsGI2dqqIKQ11M/Scheduling---Lag-and-Modes?node-id=175-3641) _for the most recent mockups._
**Manual scheduling (but predecessors overlap):**
<img class="image_resized op-uc-image op-uc-image_inline" style="width:540px;" src="/api/v3/attachments/226779/content">
**As soon as possible (start date set by predecessors):**
<img class="image_resized op-uc-image op-uc-image_inline" style="width:540px;" src="/api/v3/attachments/226780/content">
**Date picker Predecessors tab:**
<img class="image_resized op-uc-image op-uc-image_inline" style="width:540px;" src="/api/v3/attachments/226781/content">
**Options when trying to move an automatically scheduled work package in Gantt view:**
<img class="image_resized op-uc-image op-uc-image_inline" style="width:540px;" src="/api/v3/attachments/226787/content">
**Options when adding a predecessor to a manually scheduled work package in Gantt view:**
<img class="image_resized op-uc-image op-uc-image_inline" style="width:540px;" src="/api/v3/attachments/226792/content">