Since version 23.8.1 there is a new functionality that allows highlighting Parent/Child Items with red color if there are some child items out of their Parent range. This article will guide you through every possible customization on how to reflect those conflicts. It is also described how to prevent moving Child Items beyond Parent range.
Any time there is a child item scheduled out of its Parent range, you may enable this functionality to show the parent item RED or show both Child and Parent items RED.
TABLE OF CONTENTS
- How to enable showing Child Range Conflict
- Sample Cases
- Prevent dragging Child Items outside of Parent’s range
How to enable showing Child Range Conflict
This is done via a small snippet that you should put into the Advanced > Gantt Config Script section:
nextedy.gantt.config.rangeConflict = {
enabled: true,
highlightChild: true,
checkStart: true,
checkEnd: true
};
As you can notice, there are a few parameters that can be set as true/false;
enabled: decide if you want to use this functionality. If no, set this field to false and ignore the following lines or simply remove this script from the Gantt Config Script section, default is false
highlightChildren: decide if you want to highlight child items that are out of range. If false, then only the parent item would be highlighted, default is false
checkStart: decide if you want to check child items that start before the parent item starts, default is false
checkEnd: decide if you want to check child items that start after the parent item starts, default is false
Note: this functionality works if the Gantt Presentation Mode is set to Item. Otherwise, the parent items derive their schedule from children and range conflict isn't possible by definition.
Sample Cases
- enabled:false;
Just a standard view without any highlighting.
- enabled:true, highlightChildren:false, checkStart:true ,checkEnd:true
1. WorkPackage DP-538 starts before the parent Feature DP-535, so the parent item gets highlighted;
2. WorkPackage DP-538 starts before the parent Feature DP-535 and Task GN3-2712 starts before its parent WorkPackage, so both parent items get highlighted;
3. Task GN3-2712 starts before parent WP DP-538 and Task GN3-2713 finishes after parent WP DP-536 finishes.
In this case, both WPs and Tasks remain in the range of their parent Feature DP-535, so it remains not highlighted.
- enabled:true, highlightChildren:true, checkStart:true ,checkEnd:true:
1. Task GN3-2712 starts before parent WP DP-538 and is out of range of their parent Feature DP-535, + and Task GN3-2713 finishes after parent WP DP-536 so all parents and child items get highlighted.
2. With all functionality enabled if there are no items out of their parent range, everything stays blue as normal.
- enabled:true, highlightChildren:true, checkStart:false ,checkEnd:true:
1. The schedule is the same as it was in the example before, but the behavior is different as we don't check the start of items, only the end date. Task GN3-2713 finishes after parent WP DP-536 which stays in range of his parent Feature DP-535, so only WP and Tasks get highlighted.
2. In case we move Task GN3-2713 out of the range of both its parent WP DP-536 and Feature DP-535, both parent items and Task get highlighted.
Prevent dragging Child Items outside of Parent’s range
In addition to visual conflict highlighting, since version 25.4.1 you can now prevent dragging Child Items beyond their Parent's timeline. Add the following modified script into Advanced > Gantt Config Script:
nextedy.gantt.config.rangeConflict = {
preventRangeConflictMove: true,
enabled: true,
highlightChild: true,
checkStart: true,
checkEnd: true
};
preventRangeConflictMove: default is false
How it works
Note: conflict validation is also indicated when modifying the schedules via the Gantt dialog. If a Child Item is planned outside of its Parent range, a warning will appear
For any assistance, please don’t hesitate to reach out by submitting a ticket here.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article