Content
View differences
Updated by Parimal Satyal almost 4 years ago
### Note
Extracted from Epic <mention class="mention" data-id="31992" data-type="work_package" data-text="#31992">#31992</mention> related to duration.
This work package describes how values for the start date, the finish date and duration should change # Scenarios (work in response to changes to any of one of them. progress)
A lot of these are self-explanatory, but explicitly describing these behaviours helps us particularly in the testing phase to ensure that the date picker behaves as logically and intuitively as possible, whilst also reducing chances of data loss (for example, accidentally having a start date change when the user does not expect it).
### Scenarios
#### ## Scenario 1 1:
* Setup.
* Start date: Monday, February 8, 2021
* Finish date: empty
* Duration: empty
* Change
* User enters a duration of 10 days (duration in focus)
* Expected result:
* The finish date is set Friday, February 19 2021 (derived)
#### <figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/31047/content"></div></figure>
## Scenario 2
* Setup
* Start date: empty
* Finish date: empty
* Duration: empty
* Change
* User enters a duration of 10 days
* Expected result:
* No date is added
#### <figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/31048/content"></div></figure>
## Scenario 3
* Setup
* Start date: empty
* Finish date: Friday, February 19, 2021
* Duration: empty
* Change
* User enters a duration of 10 days (duration in focus).
* Expected result:
* The start date is set to Monday, February 8, 2021 (derived)
#### <figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/31049/content"></div></figure>
## Scenario 4
* Setup
* Start date: Monday, February 8, 2021
* Finish date: Friday, February 19, 2021
* Duration: 10
* Change
* User changes duration to 11 days (duration in focus).
* Expected result:
* The finish date is changed to Monday, February, 22 2021
#### <figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/31050/content"></div></figure>
## Scenario 5
* Setup
* Start date: Monday, February 8, 2021
* Finish date: Monday, February 22, 2021
* Duration: 11
* Change
* User changes duration to 10 days (duration in focus)
* Expected result:
* The finish date is changed to Friday, February, 19, 2021
* unless NWD are included, in which case, finish date is changed to Sunday, February, 21, 2021.
#### <figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/31051/content"></div></figure>
## Scenario 6
* Setup
* Start date: Tuesday, February 9, 2021
* Finish date: Friday, February 12, 2021
* Change
* Remove duration.
* Expected result
* Finish date is also removed, start date is maintained as is.
#### <figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/31052/content"></div></figure>
## Scenario 7
* Setup
* Start date: Monday, February 8, 2021
* Finish date: Wednesday, February 11, 2021
* Duration: 4
* Change
* User alters the start date to Tuesday, February 9, 2021 (start date in focus)
* Expected result
* Finish date is maintained, duration is automatically adjusted to 3 days (derived; logic = changing one date when the other is present affects duration vs. move the second date). duration)
#### <figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/31053/content"></div></figure>
## Scenario 8
* Setup
* Start date: Tuesday, February 9, 2021
* Finish date: Friday, February 12, 2021
* Duration: 4
* Change
* User alters the finish date to Feb 11, 2021 (finish date is in focus).
* Expected result
* Start date is unaffected, duration is now set to 3 days (derived from dates) dates).
#### <figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/31064/content"></div></figure>
## Scenario 9
* Setup
* Start date: empty
* Finish date: empty
* Duration: 4
* Change
* User enters the finish date of Friday, February 12, 2021 (finish date in focus).
* Expected result
* The start date is set to Tuesday, February 9, 2021 (derived from duration).
#### <figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/31055/content"></div></figure>
## Scenario 10
* Setup
* Start date: empty
* Finish date: Thursday, February 11, 2021
* Duration: empty
* Change
* User enters the start date of Tuesday, February 09, 2021 (start date in focus).
* Expected result
* Duration is set to 3 (derived from start date)
#### Scenario 11 <figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/31056/content"></div></figure>
* Setup
* Start date: Monday, February 9, 2021
* Finish date: Wednesday, February 11, 2021
* Duration: 3
* Change
* The user moves the drag handle on the left border (start date) of the box representing the work package in Gantt chart and Team planner one day to the right (to Feb 10, 2021)
* Expected result
* The duration is reduced to 2. The start date is set to Feb 10, 2021. The finish date is left unchanged.
#### ## Scenario 12 11a
* Setup
* Start date: Tuesday, February 9, 2021
* Finish date: Thursday February 11, 2021
* Duration: 3
* Change
* The user moves the Two work package by dragging it to the right so start date is Friday, Feb 12, 2021.
* Expected result packages
* The duration is maintained. Start state is now Friday, Febuary 12 2021 (as set by drag), end date is set Tuesday, Friday, February 16 (derived based on duration).
#### Scenario 13
Task 1:
* Setup
* Start date: Tuesday, February 9, 2021
* Finish date: Thursday, February 11, 2021
* Duration: 3
* Change
* The user moves the start day to Wednesday, **March 3**, 2021 (note that this is _after_ the original start date).
* Expected result
* Duration is maintained and the finish date is now moved to Friday, March 5, 2021.
#### Scenario 14
* Setup
* Start date: Tuesday, February 9, 2021
* Finish date: Thursday, February 11, 2021
* Duration: 3
* Change
* The user moves the start day to Wednesday, **February 3**, 2021 (note that this is _before_ the original start date).
* Expected result
* The start date is now Wednesday, February 3.
* The finish date is conserved (Thursday, February 11, 2021).
* The duration is updated to 7 days.
### Archived Scenarios
The following scenarios are no longer relevant because they deal with behaviour concerning follows/preceeds and parent/child relationship that do not change with the introduction of duration. They are nevertheless retained here as an archive.
#### ~~Scenario 15~~
* ~~Setup~~
* ~~Two work packages~~
* ~~Task 1:~~
* ~~Start date: Monday, 15 February, 2021~~ 2021
* ~~End End date: Wednesday, 17 February, 2021~~ 2021
* ~~Duration: 3~~ Duration: 3
* ~~Task 2:~~ Task 2:
* ~~Start Start date: empty~~ empty
* ~~End End date: empty~~ empty
* ~~Duration: empty.~~ Duration: empty.
* ~~Change~~ Change
* ~~Change Change relations such that Task 2 preceeds Task 1.~~ 1.
* ~~Expected result~~ Expected result
* ~~Dates Dates for Task 2 are derived from this "proceeds" relation.~~ relation.
* ~~Start Start date: Friday, 12 February, 2021 (dates including and after the work package this one preceedes are blocked)~~ blocked)
* ~~Duration: Duration: 1 (automatic)~~ (automatic)
* ~~End End date: Friday, 12 February, 2021 (derived from duration)~~ duration)
* ~~Warning: Warning: Reminder the start and end dates need to be before the dates of the work package this one is preceeding.~~ preceeding.
* ~~**\[open\]** **\[open\]** Invalid dates are disabled.~~ _~~This disabled. _This is something that needs to be explored further, both in terms of development effort and the impact on usability and comprehension.~~_ comprehension._
* ~~**\[open\]** **\[open\]** Possible challenge: what if the dates are limited by another work package that the user (who can modify the dates for the current work package) cannot see, because of permissions?~~ permissions?
#### ~~Scenario 16~~ <figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/31057/content"></div></figure>
## Scenario 11b (new, to be discussed)
* ~~Setup~~ Setup
* ~~Two Two work packages~~ packages
* ~~Task 1:~~ Task 1:
* ~~Start Start date: Monday, 15 February, 2021~~ 2021
* ~~End End date: Wednesday, 17 February, 2021~~ 2021
* ~~Duration: 3~~ Duration: 3
* ~~Task 2:~~ Task 2:
* ~~Start Start date: Thursday, 11 Febuary, 2021~~ 2021
* ~~End End date: Monday, 17 February, 2021~~ 2021
* ~~Duration: 5~~ Duration: 5
* ~~Change~~ Change
* ~~Change Change relations such that Task 2 preceeds Task 1.~~ 1.
* ~~**\[open, **\[open, to be discussed\]** Expected result~~ result
* ~~Dates Dates for Task 2 are changed, such that finish date is the first available date preceeding Task 1. Duration is conserved:~~ conserved:
* ~~Start Start date: Monday, 8 February, 2021 (derived from duration and finish date)~~ date)
* ~~Duration: 5~~ Duration: 5
* ~~End End date: Friday, 12 February, 2021~~ 2021
* ~~Warning: Warning: Reminder the start and end dates need to be before the dates of the work package this one is preceeding.~~ preceeding.
~~**\[note\]** **\[note\]** Today, the behaviour today seems inconsistent.~~ inconsistent.
~~For For example, in this example,~~ _~~Test a3~~_ ~~begins after~~ _~~Test a2~~_~~. When~~ _~~Test a3~~_ ~~is example, _Test a3_ begins after _Test a2_. When _Test a3_ is given a "preceeds" relationship at~~ _~~a2~~_~~, at _a2_, dates don't automatically adjust:~~ adjust:
<figure class="image op-uc-figure" style="width:75%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/31006/content"></div></figure>
~~If If we flip the relationship, (give Test~~ _~~a2~~_ ~~a Test _a2_ a "preceeds" relationship to~~ _~~Test a3),~~_ ~~the to _Test a3),_ the dates for Test a3 seem to adjust automatically so it follows a2:~~ a2:
<figure class="image op-uc-figure" style="width:75%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/31007/content"></div></figure>
~~This This second behaviour seems reasonable; a2 terminates on 22.10, so a3 automatically starts on 23.10. Do we want to preseve this? Or perhaps make the behaviour more consistent between the two cases?~~ cases?
#### ~~Scenario 17~~ ## Scenario 12a
* ~~Setup~~ Setup
* ~~Two Two work packages~~ packages
* ~~Task 1:~~ Task 1:
* ~~Start Start date: Monday, 8 February, 2021~~ 2021
* ~~End End date: Wednesday, 10 February, 2021~~ 2021
* ~~Duration: 3~~ Duration: 3
* ~~Task 2:~~ Task 2:
* ~~Start Start date: empty~~ empty
* ~~End End date: empty~~ empty
* ~~Duration: empty~~ Duration: empty
* ~~Change~~ Change
* ~~Change Change relations such that Task 2 follows Task 1.~~ 1.
* ~~Expected result~~ Expected result
* ~~Dates Dates for Task 2 are derived from this "follows" relation.~~ relation.
* ~~Start Start date: Thursday, 11 February, 2021~~ 2021
* ~~Duration: Duration: 1 (automatic)~~ (automatic)
* ~~End End date: Thursday, 11 February, 2021 (derived from duration)~~ duration)
* ~~Warning: Warning: Reminder the start and end dates need to be after the work package this one following.~~ following.
* ~~**\[open\]** **\[open\]** Invalid dates are disabled.~~ _~~This disabled. _This is something that needs to be explored further, both in terms of development effort and the impact on usability and comprehension.~~_ comprehension._
* ~~**\[open\]** **\[open\]** Possible challenge: what if the dates are limited by another work package that the user (who can modify the dates for the current work package) cannot see, because of permissions?~~ permissions?
#### ~~Scenario 18~~ <figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/31058/content"></div></figure>
## Scenario 21b (new, to be discussed)
* ~~Setup~~ Setup
* ~~Two Two work packages~~ packages
* ~~Task 1:~~ Task 1:
* ~~Start Start date: Monday, 15 February, 2021~~ 2021
* ~~End End date: Friday, 19 February, 2021~~ 2021
* ~~Duration: 5~~ Duration: 5
* ~~Task 2:~~ Task 2:
* ~~Start Start date: Tuesday, 16 Febuary, 2021~~ 2021
* ~~End End date: Thursday, 18 February, 2021~~ 2021
* ~~Duration: 3~~ Duration: 3
* ~~Change~~ Change
* ~~Change Change relations such that Task 2 follows Task 1.~~ 1.
* ~~**\[open, **\[open, to be discussed\]** Expected result~~ result
* ~~Dates Dates for Task 2 are changed, such that finish date is the first available date following Task 1. Duration is conserved:~~ conserved:
* ~~Start Start date: Monday, 22 February, 2021~~ 2021
* ~~Duration: 3~~ Duration: 3
* ~~End End date: Wednesday, 14 February, 2021~~ 2021
* ~~Warning: Warning: Reminder the start and end dates need to be after the dates of the work package this one is following.~~ following.
~~**\[note\]** **\[note\]** Today, the behaviour today seems inconsistent.~~ inconsistent.
~~For For example, in this example,~~ _~~Test a3~~_ ~~begins after~~ _~~Test a2,~~_ ~~but example, _Test a3_ begins after _Test a2,_ but before its finish date. When~~ _~~Test a2~~_ ~~is When _Test a2_ is given a "follows" relationship at~~ _~~a3~~_~~, at _a3_, dates don't automatically adjust:~~ adjust:
<figure class="image op-uc-figure" style="width:75%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/31009/content"></div></figure>
~~If If we flip the relationship, (give Test~~ _~~a2~~_ ~~a Test _a2_ a "follows" relationship to~~ _~~Test a3),~~_ ~~the to _Test a3),_ the dates for Test a3 seem to adjust automatically so it follows a2:~~ a2:
<figure class="image op-uc-figure" style="width:75%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/31008/content"></div></figure>
~~This This second behaviour seems reasonable; a2 terminates on 22.10, so a3 automatically follows on the next available day, 23.10. Do we want to this? Or perhaps make the behaviour more consistent between the two cases?~~ cases?
#### ~~Scenario 19~~ ## Scenario 13
* ~~Setup~~ Setup
* ~~Two Two work packages~~ packages
* ~~Task 1:~~ Task 1:
* ~~Start Start date: Monday, 8 February, 2021~~ 2021
* ~~End End date: Wednesday, 10 February, 2021~~ 2021
* ~~Duration: 3~~ Duration: 3
* ~~Task 2:~~ Task 2:
* ~~Start Start date: empty~~ empty
* ~~End End date: empty~~ empty
* ~~Duration: empty.~~ Duration: empty.
* ~~Change~~ Change
* ~~Change Change relations such that Task 2 is a child of Task 1.~~ 1.
* ~~Expected result~~ Expected result
* ~~Since Since the parent does not have any date information, dates and duration for Task 1 are derived from the child (as shown below)~~ below)
* ~~The The work package is automatically scheduled.~~ scheduled.
* ~~Start Start date: Monday, 8 February, 2021~~ 2021
* ~~End End date: Wednesday, 10 February, 2021~~ 2021
* ~~Duration: 10~~ Duration: 10
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/31060/content"></div></figure>
### Scenario 13: Additional cases to discuss
* **\[open\]** If the parent work package already has dates, and if they are within the range of the child:
* Current behaviour: the original dates of the parent are discarded and replaced by the start/end dates of the sum of all children.
* **\[open\]** If the parent work package already has dates, but either start or finish date (or both) are outside of the range of the child:
* Current behaviour: the original dates of the parent are discarded and replaced by the start/end dates of the sum of all children.
* Child work packages are not limited by the date range of the parent; instead, changes to the dates of the children can "stretch" or "compress" the start and finish dates of the parent.
* **\[open\]** Do we maintain current behaviour?
## Scenario 14
* Setup
* Start date: Monday, February 9, 2021
* Finish date: Wednesday, February 11, 2021
* Duration: 3
* Change
* The user moves the drag handle on the left border (start date) of the box representing the work package in Gantt chart and Team planner one day to the right (to Feb 10, 2021)
* Expected result
* The duration is reduced to 2. The start date is set to Feb 10, 2021. The finish date is left unchanged.
## Scenario 15
* Setup
* Start date: Tuesday, February 9, 2021
* Finish date: Thursday February 11, 2021
* Duration: 3
* Change
* The user moves the work package by dragging it to the right so start date is Friday, Feb 12, 2021.
* Expected result
* The duration is maintained. Start state is now Friday, Febuary 12 2021 (as set by drag), end date is set Tuesday, Friday, February 16 (derived based on duration).
## Scenario 16a
(Added in response to <mention class="mention" data-id="42086" data-type="user" data-text="@Wieland Lindenthal">@Wieland Lindenthal</mention>'s [comment on the Datepicker feature](https://community.openproject.org/projects/openproject/work_packages/41341#activity-5)).
* Setup
* Start date: Tuesday, February 9, 2021
* Finish date: Thursday, February 11, 2021
* Duration: 3
* Change
* The user moves the start day to Wednesday, **March 3**, 2021 \*\*(\*\*note that this is _after_ the original start date).
* Expected result
* Duration is maintained and the finish date is now moved to Friday, March 5, 2021.
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/31061/content"></div></figure>
## Scenario 16b (new, to be discussed)
* Setup
* Start date: Tuesday, February 9, 2021
* Finish date: Thursday, February 11, 2021
* Duration: 3
* Change
* The user moves the start day to Wednesday, **February 3**, 2021 \*\*(\*\*note that this is _before_ the original start date).
* Expected result
* The start date is now Wednesday, February 3.
* **\[open\]** The finish date is conserved (Thursday, February 11, 2021).
* **\[open\]** The duration is updated to 7 days.
Extracted from Epic <mention class="mention" data-id="31992" data-type="work_package" data-text="#31992">#31992</mention> related to duration.
This work package describes how values for the start date, the finish date and duration should change
A lot of these are self-explanatory, but explicitly describing these behaviours helps us particularly in the testing phase to ensure that the date picker behaves as logically and intuitively as possible, whilst also reducing chances of data loss (for example, accidentally having a start date change when the user does not expect it).
### Scenarios
####
* Setup.
* Start date: Monday, February 8, 2021
* Finish date: empty
* Duration: empty
* Change
* User enters a duration of 10 days (duration in focus)
* Expected result:
* The finish date is set Friday, February 19 2021 (derived)
####
##
* Setup
* Start date: empty
* Finish date: empty
* Duration: empty
* Change
* User enters a duration of 10 days
* Expected result:
* No date is added
####
##
* Setup
* Start date: empty
* Finish date: Friday, February 19, 2021
* Duration: empty
* Change
* User enters a duration of 10 days (duration in focus).
* Expected result:
* The start date is set to Monday, February 8, 2021 (derived)
####
##
* Setup
* Start date: Monday, February 8, 2021
* Finish date: Friday, February 19, 2021
* Duration: 10
* Change
* User changes duration to 11 days (duration in focus).
* Expected result:
* The finish date is changed to Monday, February, 22 2021
####
##
* Setup
* Start date: Monday, February 8, 2021
* Finish date: Monday, February 22, 2021
* Duration: 11
* Change
* User changes duration to 10 days (duration in focus)
* Expected result:
* The finish date is changed to Friday, February, 19, 2021
* unless NWD are included, in which case, finish date is changed to Sunday, February, 21, 2021.
####
##
* Setup
* Start date: Tuesday, February 9, 2021
* Finish date: Friday, February 12, 2021
* Change
* Remove duration.
* Expected result
* Finish date is also removed, start date is maintained as is.
####
##
* Setup
* Start date: Monday, February 8, 2021
* Finish date: Wednesday, February 11, 2021
* Duration: 4
* Change
* User alters the start date to Tuesday, February 9, 2021 (start date in focus)
* Expected result
* Finish date is maintained, duration is automatically adjusted to 3 days (derived; logic = changing one date when the other is present affects duration vs. move the second date).
####
##
* Setup
* Start date: Tuesday, February 9, 2021
* Finish date: Friday, February 12, 2021
* Duration: 4
* Change
* User alters the finish date to Feb 11, 2021 (finish date is in focus).
* Expected result
* Start date is unaffected, duration is now set to 3 days (derived from dates)
####
##
* Setup
* Start date: empty
* Finish date: empty
* Duration: 4
* Change
* User enters the finish date of Friday, February 12, 2021 (finish date in focus).
* Expected result
* The start date is set to Tuesday, February 9, 2021 (derived from duration).
####
##
* Setup
* Start date: empty
* Finish date: Thursday, February 11, 2021
* Duration: empty
* Change
* User enters the start date of Tuesday, February 09, 2021 (start date in focus).
* Expected result
* Duration is set to 3 (derived from start date)
#### Scenario 11
* Setup
* Start date: Monday, February 9, 2021
* Finish date: Wednesday, February 11, 2021
* Duration: 3
* Change
* The user moves the drag handle on the left border (start date) of the box representing the work package in Gantt chart and Team planner one day to the right (to Feb 10, 2021)
* Expected result
* The duration is reduced to 2. The start date is set to Feb 10, 2021. The finish date is left unchanged.
####
* Setup
* Start date: Tuesday, February 9, 2021
* Finish date: Thursday February 11, 2021
* Duration: 3
* Change
* The user moves the
* Expected result
* The duration is maintained. Start state is now Friday, Febuary 12 2021 (as set by drag), end date is set Tuesday, Friday, February 16 (derived based on duration).
#### Scenario 13
* Start date: Tuesday, February 9, 2021
* Finish date: Thursday, February 11, 2021
* Duration: 3
* Change
* The user moves the start day to Wednesday, **March 3**, 2021 (note that this is _after_ the original start date).
* Expected result
* Duration is maintained and the finish date is now moved to Friday, March 5, 2021.
#### Scenario 14
* Setup
* Start date: Tuesday, February 9, 2021
* Finish date: Thursday, February 11, 2021
* Duration: 3
* Change
* The user moves the start day to Wednesday, **February 3**, 2021 (note that this is _before_ the original start date).
* Expected result
* The start date is now Wednesday, February 3.
* The finish date is conserved (Thursday, February 11, 2021).
* The duration is updated to 7 days.
### Archived Scenarios
The following scenarios are no longer relevant because they deal with behaviour concerning follows/preceeds and parent/child relationship that do not change with the introduction of duration. They are nevertheless retained here as an archive.
#### ~~Scenario 15~~
* ~~Setup~~
* ~~Two work packages~~
* ~~Task 1:~~
* ~~Start date: Monday, 15 February, 2021~~
* ~~End
* ~~Duration: 3~~
* ~~Task 2:~~
* ~~Start
* ~~End
* ~~Duration: empty.~~
* ~~Change~~
* ~~Change
* ~~Expected result~~
* ~~Dates
* ~~Start
* ~~Duration:
* ~~End
* ~~Warning:
* ~~**\[open\]**
* ~~**\[open\]**
#### ~~Scenario 16~~
* ~~Two
* ~~Task 1:~~
* ~~Start
* ~~End
* ~~Duration: 3~~
* ~~Task 2:~~
* ~~Start
* ~~End
* ~~Duration: 5~~
* ~~Change~~
* ~~Change
* ~~**\[open,
* ~~Dates
* ~~Start
* ~~Duration: 5~~
* ~~End
* ~~Warning:
~~**\[note\]**
~~For
<figure class="image op-uc-figure" style="width:75%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/31006/content"></div></figure>
~~If
<figure class="image op-uc-figure" style="width:75%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/31007/content"></div></figure>
~~This
#### ~~Scenario 17~~
* ~~Setup~~
* ~~Two
* ~~Task 1:~~
* ~~Start
* ~~End
* ~~Duration: 3~~
* ~~Task 2:~~
* ~~Start
* ~~End
* ~~Duration: empty~~
* ~~Change~~
* ~~Change
* ~~Expected result~~
* ~~Dates
* ~~Start
* ~~Duration:
* ~~End
* ~~Warning:
* ~~**\[open\]**
* ~~**\[open\]**
#### ~~Scenario 18~~
* ~~Two
* ~~Task 1:~~
* ~~Start
* ~~End
* ~~Duration: 5~~
* ~~Task 2:~~
* ~~Start
* ~~End
* ~~Duration: 3~~
* ~~Change~~
* ~~Change
* ~~**\[open,
* ~~Dates
* ~~Start
* ~~Duration: 3~~
* ~~End
* ~~Warning:
~~**\[note\]**
~~For
<figure class="image op-uc-figure" style="width:75%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/31009/content"></div></figure>
~~If
<figure class="image op-uc-figure" style="width:75%;"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/31008/content"></div></figure>
~~This
#### ~~Scenario 19~~
* ~~Setup~~
* ~~Two
* ~~Task 1:~~
* ~~Start
* ~~End
* ~~Duration: 3~~
* ~~Task 2:~~
* ~~Start
* ~~End
* ~~Duration: empty.~~
* ~~Change~~
* ~~Change
* ~~Expected result~~
* ~~Since
* ~~The
* ~~Start
* ~~End
* ~~Duration: 10~~
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/31060/content"></div></figure>
### Scenario 13: Additional cases to discuss
* **\[open\]** If the parent work package already has dates, and if they are within the range of the child:
* Current behaviour: the original dates of the parent are discarded and replaced by the start/end dates of the sum of all children.
* **\[open\]** If the parent work package already has dates, but either start or finish date (or both) are outside of the range of the child:
* Current behaviour: the original dates of the parent are discarded and replaced by the start/end dates of the sum of all children.
* Child work packages are not limited by the date range of the parent; instead, changes to the dates of the children can "stretch" or "compress" the start and finish dates of the parent.
* **\[open\]** Do we maintain current behaviour?
## Scenario 14
* Setup
* Start date: Monday, February 9, 2021
* Finish date: Wednesday, February 11, 2021
* Duration: 3
* Change
* The user moves the drag handle on the left border (start date) of the box representing the work package in Gantt chart and Team planner one day to the right (to Feb 10, 2021)
* Expected result
* The duration is reduced to 2. The start date is set to Feb 10, 2021. The finish date is left unchanged.
## Scenario 15
* Setup
* Start date: Tuesday, February 9, 2021
* Finish date: Thursday February 11, 2021
* Duration: 3
* Change
* The user moves the work package by dragging it to the right so start date is Friday, Feb 12, 2021.
* Expected result
* The duration is maintained. Start state is now Friday, Febuary 12 2021 (as set by drag), end date is set Tuesday, Friday, February 16 (derived based on duration).
## Scenario 16a
(Added in response to <mention class="mention" data-id="42086" data-type="user" data-text="@Wieland Lindenthal">@Wieland Lindenthal</mention>'s [comment on the Datepicker feature](https://community.openproject.org/projects/openproject/work_packages/41341#activity-5)).
* Setup
* Start date: Tuesday, February 9, 2021
* Finish date: Thursday, February 11, 2021
* Duration: 3
* Change
* The user moves the start day to Wednesday, **March 3**, 2021 \*\*(\*\*note that this is _after_ the original start date).
* Expected result
* Duration is maintained and the finish date is now moved to Friday, March 5, 2021.
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/31061/content"></div></figure>
## Scenario 16b (new, to be discussed)
* Setup
* Start date: Tuesday, February 9, 2021
* Finish date: Thursday, February 11, 2021
* Duration: 3
* Change
* The user moves the start day to Wednesday, **February 3**, 2021 \*\*(\*\*note that this is _before_ the original start date).
* Expected result
* The start date is now Wednesday, February 3.
* **\[open\]** The finish date is conserved (Thursday, February 11, 2021).
* **\[open\]** The duration is updated to 7 days.