Content
View differences
Updated by Christophe Bliard over 1 year ago
**Example:**
[https://qa.openproject-edge.com/projects/7-lorem-ipsum-dolor-sit-amet-3/gantt?query\_id=3746&name=all\_open](https://qa.openproject-edge.com/projects/7-lorem-ipsum-dolor-sit-amet-3/gantt?query_id=3746&name=all_open)
**Context:**
* Currently, the parent's dates are derived from those of children.
* However, even if you set all children to manual scheduling mode and move them wildly outside the original date range (such that no child corresponds to those dates), the parent's dates remain unchanged. In other words, once a child goes to manual scheduling, it will not update the parent's date.
**Question:**
* Does it make sense to keep this behaviour? Isn't it odd for the parent to now have dates that correspond to nothing at all, yet it is in automatic mode and dates can't be changed?
**Suggestion:**
* If a parent _only_ has children that are manually scheduled, it should remain in automatic scheduling but there should be no dates.
* In other words, the parent only gets its dates from non-manually scheduled children.
* \[cbl\] I disagree. As being manually scheduled is now the default, it means that if a work package with dates becomes the child of another work package, then instead of inheriting its child dates, it will have no dates. That's a big change from how it worked before. It should rather take children dates, like before, but regardless of the scheduling modes of the children. That would be more consistent.
**Decision:**
* A parent in automatic scheduling mode will have its dates derived from children dates
* if none of the children have any dates, the parent will not have any dates
* if some children have start dates, the parent start date will be the earliest start date of the children
* if some children have due dates, the parent due date will be the latest due date of the children
* to change parent dates freely, its scheduling mode must change to manual. Dates can then be anything.
* A parent in automatic scheduling mode and being also a successor will still have its dates derived from children dates.
* If children are automatically scheduled, they will be influenced by the parent predecessor as an indirect predecessor. This will reschedule the children dates which will in turn reschedule the parent dates.
* In the date picker, the parent indicates "_The dates are determined by child work packages._", as specified in ##59539, which helps understanding why it may start before the predecessor.
<br>
[https://qa.openproject-edge.com/projects/7-lorem-ipsum-dolor-sit-amet-3/gantt?query\_id=3746&name=all\_open](https://qa.openproject-edge.com/projects/7-lorem-ipsum-dolor-sit-amet-3/gantt?query_id=3746&name=all_open)
**Context:**
* Currently, the parent's dates are derived from those of children.
* However, even if you set all children to manual scheduling mode and move them wildly outside the original date range (such that no child corresponds to those dates), the parent's dates remain unchanged. In other words, once a child goes to manual scheduling, it will not update the parent's date.
**Question:**
* Does it make sense to keep this behaviour? Isn't it odd for the parent to now have dates that correspond to nothing at all, yet it is in automatic mode and dates can't be changed?
**Suggestion:**
* If a parent _only_ has children that are manually scheduled, it should remain in automatic scheduling but there should be no dates.
* In other words, the parent only gets its dates from non-manually scheduled children.
* \[cbl\] I disagree. As being manually scheduled is now the default, it means that if a work package with dates becomes the child of another work package, then instead of inheriting its child dates, it will have no dates. That's a big change from how it worked before. It should rather take children dates, like before, but regardless of the scheduling modes of the children. That would be more consistent.
**Decision:**
* A parent in automatic scheduling mode will have its dates derived from children dates
* if none of the children have any dates, the parent will not have any dates
* if some children have start dates, the parent start date will be the earliest start date of the children
* if some children have due dates, the parent due date will be the latest due date of the children
* to change parent dates freely, its scheduling mode must change to manual. Dates can then be anything.
* A parent in automatic scheduling mode and being also a successor will still have its dates derived from children dates.
* If children are automatically scheduled, they will be influenced by the parent predecessor as an indirect predecessor. This will reschedule the children dates which will in turn reschedule the parent dates.
* In the date picker, the parent indicates "_The dates are determined by child work packages._", as specified in ##59539, which helps understanding why it may start before the predecessor.
<br>