**As** a project portfolio manager
**I want to** have phases Begin of the deletion and gatesEnd of the deletion adjusted automatically based on changes of preceding Begin of the insertionphases
End of the insertion Begin of the deletion phases/gates
End of the deletion **so that** rescheduling Begin of the deletion ofEnd of the deletion is simpler and less error prone.

### Acceptance criteria

* Begin of the insertionPhasesEnd of the insertion Begin of the deletion Defined in the epic <mention class="mention" data-id="59177" data-type="work_package" data-text="#59177">#59177</mention> 


### Out of scope

* Backwards planning

* Durations


### Outdated specs - to be reworked

* All changes

* Stages and gatesEnd of the deletion are automatically (re)scheduled to the extend the information provided by the user allows for. Begin of the insertionWheneverEnd of the insertion Begin of the deletion

* SeeEnd of the deletion the Begin of the insertionfinish date ofEnd of the insertion Begin of the deletion **Scenarios** section forEnd of the deletion a Begin of the insertionphase changes,End of the insertion Begin of the deletion detailed specification.

* \[open\] Are allEnd of the deletion the Begin of the insertionsucceeding phase's start date is updated to be onEnd of the insertion Begin of the deletion scenarios correct?

* Automatic scheduling happens as soon as two values out ofEnd of the deletion the Begin of the insertionnon working day after theEnd of the insertion Begin of the deletion three involved attributes (start date, endEnd of the deletion date Begin of the insertionselectedEnd of the insertion Begin of the deletion & duration) are set (analogousEnd of the deletion to Begin of the insertionbe the finish date of the predecessor.
End of the insertion Begin of the deletion work packages).

End of the deletion * Begin of the insertionIf the succeeding phase hasEnd of the insertion Begin of the deletion For gates, as they haveEnd of the deletion a Begin of the insertionfinish date setEnd of the insertion Begin of the deletion fixed duration of 0End of the deletion and Begin of the insertionhad a startEnd of the insertion Begin of the deletion only one date, thatEnd of the deletion date Begin of the insertionset thatEnd of the insertion is Begin of the insertionnow changed,End of the insertion the Begin of the insertionfinish date is updatedEnd of the insertion Begin of the deletion only value that needsEnd of the deletion to Begin of the insertionpreserve the durationEnd of the insertion Begin of the deletion be filled.

* Project start/finish dates behave similar to gates.

* Scheduling a predecessor (by providing two outEnd of the deletion of the Begin of the insertionsucceeding phase. The duration isEnd of the insertion Begin of the deletion three values, orEnd of the deletion the Begin of the insertionnumber of non working days betweenEnd of the insertion Begin of the deletion one value for a gate), can lead toEnd of the deletion the Begin of the deletion successor being rescheduled in turn (e.g. a succeeding stage/gate receives aEnd of the deletion start Begin of the deletion date) which can continue as long as each successor is completely specified.

* Since gatesEnd of the deletion and Begin of the insertiontheEnd of the insertion Begin of the deletion also projectEnd of the deletion finish dates Begin of the insertion(both dates included). The finish date might thusEnd of the insertion Begin of the deletion only require a single value toEnd of the deletion be Begin of the insertionmoved intoEnd of the insertion Begin of the deletion scheduled, they will always be scheduled once a predecessor is complete.

* Scheduling a successor (by providing two out ofEnd of the deletion the Begin of the insertionfutureEnd of the insertion Begin of the deletion three values,End of the deletion or the Begin of the insertionpast.
* IfEnd of the insertion Begin of the deletion one value for a gate), can lead toEnd of the deletion the Begin of the insertionsucceeding phase hasEnd of the insertion Begin of the deletion predecessor being rescheduled in turn (e.g.End of the deletion a Begin of the insertionfinish date set but did not haveEnd of the insertion Begin of the deletion preceding stage/gate receivesEnd of the deletion a Begin of the insertionstart date set before, no duration existed before. Therefore, the successor'sEnd of the insertion finish Begin of the insertiondate does not need to be updatedEnd of the insertion Begin of the deletion date) which can continueEnd of the deletion as long as Begin of the insertionitEnd of the insertion Begin of the deletion each successorEnd of the deletion is Begin of the insertionat least on the date of theEnd of the insertion Begin of the deletion completely specified.

* Since gates and also projectEnd of the deletion start Begin of the insertiondate. If the finish dateEnd of the insertion Begin of the deletion dates only require a single value to be scheduled, they will always be scheduled once a successorEnd of the deletion is Begin of the insertionbefore the newly set start date, the finishEnd of the insertion Begin of the deletion complete.

* Stages do not receive a singleEnd of the deletion date Begin of the deletion when being automatically scheduled. e.g. if a preceding gateEnd of the deletion is Begin of the insertionupdated to be onEnd of the insertion Begin of the deletion set,End of the deletion the Begin of the insertionsame date as theEnd of the insertion Begin of the deletion succeeding stage does not receive aEnd of the deletion start date. Begin of the insertion
End of the insertion Begin of the deletion

End of the deletion * Begin of the insertionThis continues untilEnd of the insertion Begin of the deletion However, if two values are then available (see above),End of the deletion the Begin of the insertionend of the chain of phases is reached.
End of the insertion Begin of the deletion stage will be scheduled.

End of the deletion * Begin of the insertionAutomatic scheduling happens fully automatic.End of the insertion Begin of the deletion End of the deletion The Begin of the insertionuserEnd of the insertion Begin of the deletion reason for thisEnd of the deletion is Begin of the insertionnot asked for confirmation.
* Even if the user hasn't yet specified theEnd of the insertion Begin of the deletion that stages always require twoEnd of the deletion dates Begin of the insertionfor durations of all the phases, automatic scheduling will start as soon andEnd of the insertion to Begin of the insertionthe extend where durations of succeeding phases are present.
End of the insertion Begin of the deletion be defined.

End of the deletion * Begin of the insertionAutomatic scheduling only happens forward. Therefore, setting a finishEnd of the insertion Begin of the deletion TheEnd of the deletion date Begin of the insertionon a phase thatEnd of the insertion Begin of the deletion the stage would inherit from its neighbourEnd of the deletion is Begin of the insertionbefore its start date will resultEnd of the insertion Begin of the deletion displayedEnd of the deletion in Begin of the insertionan error being displayed.End of the insertion Begin of the deletion the table (grayed out).

* End of the deletion The Begin of the insertionstartEnd of the insertion date Begin of the insertionwill not be automatically changed. Even ifEnd of the insertion the Begin of the insertionprovided finish dateEnd of the insertion Begin of the deletion stage would inherit from its neighbourEnd of the deletion is Begin of the insertionnot beforeEnd of the insertion Begin of the deletion preselected inEnd of the deletion the Begin of the insertionstart date, the duration is not kept in this case, but changes.
End of the insertion Begin of the deletion date picker. The user can choose to select a different value.

End of the deletion * Begin of the insertionPhases active in a projectEnd of the insertion Begin of the deletion Active stages/gatesEnd of the deletion are considered to be following each other based on the sort order in the administration. Begin of the insertion
End of the insertion Begin of the deletion

End of the deletion * Begin of the deletion End of the deletion In case a Begin of the insertionphaseEnd of the insertion Begin of the deletion stage/gateEnd of the deletion is inactive in a project, the next active Begin of the insertionphaseEnd of the insertion Begin of the deletion stage/gateEnd of the deletion is considered to be the successor. Multiple inactive Begin of the insertionphasesEnd of the insertion Begin of the deletion stages/gatesEnd of the deletion can be ignored that way. Begin of the insertion
End of the insertion Begin of the deletion

End of the deletion * Begin of the insertionInactive phasesEnd of the insertion Begin of the deletion Stages/gates not active in the projectEnd of the deletion are not scheduled. Begin of the insertion
End of the insertion Begin of the deletion In case a stage/gate is inactivated, it keeps its dates.

End of the deletion * Begin of the insertionIfEnd of the insertion Begin of the deletion The project start date is considered to beEnd of the deletion the Begin of the insertionuser removesEnd of the insertion Begin of the deletion first gate forEnd of the deletion the Begin of the deletion sake of automatic scheduling.

* The projectEnd of the deletion finish date Begin of the deletion is considered to be the last gate for the sakeEnd of the deletion of Begin of the deletion automatic scheduling.

* Non working days

* Are displayed in the date picker

* Are allowed values for start and end date and do not count towards the duration.

* This is subject to change, see "out of scope".

* Gaps (implicit distance between the end date ofEnd of the deletion a Begin of the insertionphase, this also removesEnd of the insertion Begin of the deletion preceding andEnd of the deletion the start date of Begin of the insertiontheEnd of the insertion Begin of the deletion aEnd of the deletion succeeding Begin of the insertionphase.End of the insertion Begin of the deletion lifecycle step) are not allowed.

* End of the deletion The Begin of the insertionfinishEnd of the insertion Begin of the deletion lag (explicit distance between the endEnd of the deletion date of Begin of the deletion a preceding andEnd of the deletion the Begin of the deletion start date of aEnd of the deletion succeeding Begin of the insertionphaseEnd of the insertion Begin of the deletion lifecycle step)End of the deletion is Begin of the insertionnot touchedEnd of the insertion Begin of the deletion for now always 0.

* This is subject to changeEnd of the deletion in Begin of the insertionthis case.
End of the insertion Begin of the deletion a later feature.

End of the deletion * Begin of the insertionIfEnd of the insertion Begin of the deletion The lag of 0 means

* A stage succeeding another stage will haveEnd of the deletion a Begin of the insertionphaseEnd of the insertion Begin of the deletion start date thatEnd of the deletion is Begin of the insertionactivated, dependingEnd of the insertion on Begin of the insertionits position inEnd of the insertion the Begin of the insertionsort order, it may then automatically receiveEnd of the insertion Begin of the deletion next working day relative to the end date of the preceding stage's end date.

* A gate succeedingEnd of the deletion a Begin of the insertionnew startEnd of the insertion Begin of the deletion stage will have a date that is on the same date as the preceding stage's endEnd of the deletion date. Begin of the insertion
End of the insertion Begin of the deletion

End of the deletion * Begin of the insertionIf it already hadEnd of the insertion Begin of the deletion A stage succeedingEnd of the deletion a Begin of the insertionduration (start/finishEnd of the insertion Begin of the deletion gate will have a startEnd of the deletion date Begin of the insertionset), its finish date would then also be updatedEnd of the insertion Begin of the deletion that is on the next working day relativeEnd of the deletion to Begin of the insertionkeepEnd of the insertion the Begin of the insertionduration. This might then trigger a reschedulingEnd of the insertion Begin of the deletion dateEnd of the deletion of Begin of the insertionsucceeding phases.
* If it had no duration,End of the insertion the Begin of the deletion preceding stage's date.


### **Scenarios**

(Within the scope of the scenarios, when gates are mentioned, this includes the projectEnd of the deletion start Begin of the deletion and finishEnd of the deletion date Begin of the deletion but not the other way around.)

#### **If the dates/duration were not filled completely before**

As stated in the acceptance criteria, scheduling happens when:

* For stages: two out of three values (start date, end date, duration) are set (oneEnd of the deletion might Begin of the insertionbeEnd of the insertion Begin of the deletion have beenEnd of the deletion set Begin of the insertionbutEnd of the insertion Begin of the deletion before)

* For gate:End of the deletion the Begin of the insertionfinishEnd of the insertion date Begin of the insertionwould remain unset. This mightEnd of the insertion Begin of the deletion is set


Since active life cycle steps are always considered to beEnd of the deletion in Begin of the insertionturn unsetEnd of the insertion Begin of the deletion a follows relationship, scheduling a step can lead toEnd of the deletion the Begin of the insertionstart dateEnd of the insertion Begin of the deletion successor/predecessor receiving the necessary information to be automatically scheduled in turn. Scheduling can thus propagate both along the lineEnd of the deletion of Begin of the deletion successors as well as alongEnd of the deletion the Begin of the insertionsucceeding phase.
* IfEnd of the insertion Begin of the deletion line of predecessors. This continues untilEnd of the deletion a Begin of the insertionphaseEnd of the insertion Begin of the deletion stageEnd of the deletion is Begin of the insertiondeactivated,End of the insertion Begin of the deletion met that has then only one value set or untilEnd of the deletion the Begin of the insertiondatesEnd of the insertion Begin of the deletion endEnd of the deletion of the Begin of the insertiondeactivated phase are kept. The newEnd of the insertion chain Begin of the insertionof active phasesEnd of the insertion is Begin of the insertionthenEnd of the insertion Begin of the deletion reached. Gates, since they only require a single value are always continued to be automaticallyEnd of the deletion scheduled Begin of the insertionfromEnd of the insertion Begin of the deletion and will schedule successors/predecessors in turn:

* If scheduling a succeeding gate: Its date will be onEnd of the deletion the Begin of the insertionposition ofEnd of the insertion Begin of the deletion date (for a preceding gate) orEnd of the deletion the Begin of the insertiondeactivated phase onward.
End of the insertion Begin of the deletion end date (for a preceding stage)

End of the deletion * Begin of the insertionAddingEnd of the insertion Begin of the deletion If scheduling a preceding gate: Its date will be on the date (for a succeeding gate)End of the deletion or Begin of the insertionremoving non working days triggersEnd of the insertion Begin of the deletion one date before the start date (forEnd of the deletion a Begin of the insertionrescheduling of all phases spanningEnd of the insertion Begin of the deletion succeeding gate)


If a stage is met it will receive :

* If scheduling a succeeding stage: Its start date will be 1 day afterEnd of the deletion the Begin of the insertionaffected days. In turn, successors of those phases are also rescheduled. The goalEnd of the insertion Begin of the deletion date (for a preceding gate) or one 1 day after the end date (for a preceding stage)

* If scheduling a preceding stage: Its end date will be on the date (for a succeed gate) or one day before the start date (for a preceding stage)


(\[open\] will the value be persistedEnd of the deletion in Begin of the insertionthisEnd of the insertion Begin of the deletion the database inEnd of the deletion case Begin of the deletion the stage would end up with only the start or finish date. The fontendEnd of the deletion is to Begin of the insertionkeepEnd of the insertion Begin of the deletion display that date grayed)

The stage thus receiving a start/end date might then have two out ofEnd of the deletion the Begin of the deletion three necessary values, and will be rescheduled and might continue to schedule in turn:

* If the stage used to have aEnd of the deletion duration Begin of the insertionunchanged.
End of the insertion Begin of the deletion only, it will then get its start/end date calculated:

End of the deletion * Begin of the insertionDeleting, adding, reordering phases inEnd of the insertion Begin of the deletion start date + (duration - 1)

* end date - (duration - 1)

* IfEnd of the deletion the Begin of the insertionglobal administration potentially affects projects since they mightEnd of the insertion Begin of the deletion stage used to have a start/end date only, it will get its duration calculated:

* end date - start date + 1


#### **If date/duration wereEnd of the deletion already Begin of the insertionhave phases activeEnd of the insertion Begin of the deletion provided before**

Updating an already completely specified stage can be done in three waysEnd of the deletion and Begin of the insertionscheduled. For now, no automaticEnd of the insertion Begin of the deletion each leads to a differentEnd of the deletion rescheduling Begin of the insertionhappens in this case. ButEnd of the insertion Begin of the deletion ofEnd of the deletion the Begin of the insertionfirst timeEnd of the insertion Begin of the deletion successor/predecessor:

IfEnd of the deletion the Begin of the insertionuser touchesEnd of the insertion Begin of the deletion start date is updated,End of the deletion the Begin of the insertionlifecycle,End of the insertion Begin of the deletion duration is increased/decreased accordingly. Because a date range picker is employed,End of the deletion the Begin of the insertionscheduleEnd of the insertion Begin of the deletion user's intendEnd of the deletion is Begin of the insertionupdated. Again,End of the insertion Begin of the deletion clear. The preceding stages/gates are updating accordingly without changing their duration.

IfEnd of the deletion the Begin of the insertiongoalEnd of the insertion Begin of the deletion finish dateEnd of the deletion is Begin of the insertionto keepEnd of the insertion Begin of the deletion updated,End of the deletion the duration Begin of the insertionofEnd of the insertion Begin of the deletion is increased/decreased accordingly. Because a date range picker is employed,End of the deletion the Begin of the insertionphases unchanged.

### Out of scopeEnd of the insertion Begin of the deletion user's intend is clear. The succeeding stages/gates are updating accordingly without changing their duration.End of the deletion

Begin of the insertion* Backwards planning
* Durations
* Gaps (implicit distance betweenEnd of the insertion Begin of the deletion IfEnd of the deletion the Begin of the insertionendEnd of the insertion Begin of the deletion duration is increased/decreased, the finishEnd of the deletion date Begin of the deletion is updated accordingly. Then, the succeeding stages/gates are moved by the same amount without changing their duration.

For gates and the project start/finish date, the reschedulingEnd of the deletion of Begin of the deletion the predecessors/successors happens accordingly.

#### IfEnd of the deletion a Begin of the deletion dates/duration is removed

If the dates of a stage is removed, the duration is removed. If the duration is removed, the dates are removed. Then, the succeeding andEnd of the deletion preceding Begin of the deletion stages also might loose their datesEnd of the deletion and Begin of the insertiontheEnd of the insertion Begin of the deletion duration. A gate encountered like this, will always return its date. A preceding stage will loose its end date and duration. A succeeding stage will lose itsEnd of the deletion start date Begin of the insertionofEnd of the insertion Begin of the deletion and duration.

(\[open\] same as for when receiving dates but not having enough data to reschedule, it is unclear whether the stage should also loose its other date in the backend or wether to still keep. In either case it is to be displayed grayed out in the frontend)

The removal will not continue on afterEnd of the deletion a Begin of the deletion stage is met.

#### If a stage/gate is deactivated

If a gate is deactivated, no rescheduling needs to take place. The gate will loose its date.

If a stage is deactivated, its start/finish date are removed but its duration is kept. TheEnd of the deletion succeeding Begin of the insertionlifecycle step)End of the insertion Begin of the deletion stage/gate and its successorsEnd of the deletion are Begin of the insertionnot allowed.
* TheEnd of the insertion Begin of the deletion moved into the past so that noEnd of the deletion lag Begin of the insertion(explicit distanceEnd of the insertion between the Begin of the insertionendEnd of the insertion Begin of the deletion disabled stage's predecessor and successor remains.

(\[open\] This currently contradicts the figma files)

#### If a stage/gate is activated

If a gate is activated the gate receives the predecessors finishEnd of the deletion date Begin of the insertionofEnd of the insertion Begin of the deletion (stage) or date (gate) for its own date.

IfEnd of the deletion a Begin of the insertionpreceding andEnd of the insertion Begin of the deletion stage is activated, it receivesEnd of the deletion the Begin of the deletion day after the predecessors finish date (stage) or date (gate) as itsEnd of the deletion start Begin of the deletion date. Its finish is the startEnd of the deletion date Begin of the deletion plus the potentially stored duration. If no duration is stored, a durationEnd of the deletion of Begin of the deletion 1 is assumed so the finish date is on the same date of the start date. Succeeding stages and gates are rescheduled into the future accordingly.

(\[open\] This currently contradicts the figma files)

#### Other scenarios

* Scenarios where the LifeCycleDefinitions are modified:

* WhenEnd of the deletion a Begin of the insertionsucceeding lifecycle step) cannot be set byEnd of the insertion Begin of the deletion definition is added:

* Expected result: No rescheduling.

* When a definition is deleted:

* Expected result: No rescheduling.

* When 2 definitions are reordered:

* Currently, no automatic rescheduling happens. ButEnd of the deletion the Begin of the deletion first time theEnd of the deletion user Begin of the insertioncurrently. By that, itEnd of the insertion Begin of the deletion touches the lifecycle, the out of order lifecycle steps are reordered keeping their duration unchanged.

* Scenarios where Non Working days or Non Working weekdays are modified:

* When a Non Working Day or WeekdayEnd of the deletion is Begin of the insertioneffectively always 0.
End of the insertion Begin of the deletion added or removed:

End of the deletion * Begin of the deletion Expected result: No rescheduling.


**Out of scope**

* Non working days are for now available start/end dates and count towards the duration.

* End of the deletion This is subject to change Begin of the insertioninEnd of the insertion Begin of the deletion but doing so would increase the complexity.

* AddingEnd of the deletion a Begin of the insertionlater feature.End of the insertion Begin of the deletion lag value other than 0 will be implemented later.End of the deletion