Content
View differences
Updated by Parimal Satyal over 3 years ago
**As** a user
**I want to** have a consistent and understandable inheritance of dates (start/finish) up and down the work package ancestor chain
**so that** I know what is going to happen when I alter the work package hierarchy (e.g. add a child/parent)
**Acceptance criteria**
* Inheritance of dates (finish/start) up the ancestor chain (from child to parent) should always only be for the date that is set. E.g: E.g:
* If neither When setting a start date on a child and both the parent nor as well as the child has did not have any dates set:
* Setting a left, only the start date on a child will mean that that of the parent will inhert _only_ is to be set to the start same date from as the child's start date. Finish date and duration (if present) remain unchanged.
* The same is true for Both finish date; when the child only has a finish date, the parent can only inherit this finish date, and start date and duration (if present) remain are to be unchanged.
* Inheritance of dates (finish/start) down the ancestor chain (from parent to child) should always only be for the dates date that are set. is set. E.g:
* So when the parent has start _and_ finish dates:
* A new When creating a child (regardless of whether it is the first or a subsequent one created one) via any means) inherits both of means, and the dates (and naturally also the duration).
* When the parent only has one a start date (start _or_ finish):
* A new and a finish date set, the child (regardless is to receive both of whether it is the first or a subsequent one created via any means) inherits _only_ this date; dates (and the other date and duration remain unchanged. duration)
* TBD: If an existing a work package is turned into a child, the new parent will should receive only the date or dates (start/finish) that are set on the new child.
* It inherits child. If the start date of the earlier child and already has dates set, the finish date minimum of the latest child.
* If no child has a start date, then dates are used for the parent will have no parent's start date (inheriting and the finish date maximum of the latest child).
* If no child has a finish date, then dates are used for the parent will have no parent's finish date (inheriting the start date of the earliest child). date.
* When milestones become a child, their unique Open: How to handle the one date will be considered start and finish, and of milestones? Is it will behave both the same start as a one-day work package (with well as the same start and finish dates). date?
#### _Current behaviour_
* Creating the first child from within the relations tab:
* If the parent has a start date and no date is provided for the child by the user: The child's start date is set to the parent's start date. The parent's finish date is set to the start date of the child (which is the same as the parent's start date) and the duration is set to 1.
* Creating the second, third, ... child from within the relation tab:
* If the parent has a start date and no date is provided for the child by the user: The child's start date is not set. No change is done on the parent's dates.
* Assigning a parent to an already existing child (e.g. via "Set parent" on the full/split screen or by indenting on the Gantt chart)
* The dates of the parent are overwritten. This includes parent dates being deleted in case the child does not have dates.
**I want to** have a consistent and understandable inheritance of dates (start/finish) up and down the work package ancestor chain
**so that** I know what is going to happen when I alter the work package hierarchy (e.g. add a child/parent)
**Acceptance criteria**
* Inheritance of dates
* If neither
* Setting a
* The same is true for
* Inheritance of dates (finish/start) down the ancestor chain (from parent to child) should always only be for the dates
* So when the parent has start _and_ finish dates:
* A new
* When the parent only has one
* A new
*
* It inherits
* If no child has a start date, then
* If no child has a finish date, then
* When milestones become a child, their unique
#### _Current behaviour_
* Creating the first child from within the relations tab:
* If the parent has a start date and no date is provided for the child by the user: The child's start date is set to the parent's start date. The parent's finish date is set to the start date of the child (which is the same as the parent's start date) and the duration is set to 1.
* Creating the second, third, ... child from within the relation tab:
* If the parent has a start date and no date is provided for the child by the user: The child's start date is not set. No change is done on the parent's dates.
* Assigning a parent to an already existing child (e.g. via "Set parent" on the full/split screen or by indenting on the Gantt chart)
* The dates of the parent are overwritten. This includes parent dates being deleted in case the child does not have dates.