Lighter colored parts in bars of parent tasks when sub-tasks exceed duration in Gantt chart
Hi there,
I have een searching for a while about the use and meaning of the color code on parent tasks in the Gantt chart.
When the time range of the parent task does not encompass all sub-tasks, the parent task bar is extended in a lighter color for that time range while the start/finish datesin the table view of the parent task are still kept to the darker colored time segment.
Please find below example screenshot:
Is this just meant as a visual guide to let you know, that the parent task is not covering the entire time it takes for all subtasks?
Why are parent tasks not just automatically adapted to early start date - latest finished date of all sub-tasks?
Thanks for your input!
Stephan,
Hi Stephan Mauer, welcome to the Community!
I think that in this case, we'd need help from our Support team, so I'm going to raise a ticket for you now. You'll receive a notification soon and someone from Support will reach out to you.
Please let me know if you have any other questions!
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
If i remeber correctly Wrike asks you in list view if you want to apply the time constraints of tasks to parent tasks once you hit up the parent task. Not 100% on that though.
Hey again, everyone!
I thought I'd post a reply from our Support here:
This lighter color indicates that the parent task is not covering the entire time it takes for all subtasks.
If you would like to have parent task's dates to be rolled up to subtask's dates, please enable Gantt Chart Roll up in Wrike Labs as per this instruction: Roll Up Dates in Gantt Chart.
Hope it helps 🙂
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
Jan-Christoph and Lisa, Thanks for helping out with that!
Stephan.
I am having an issue with setting a predecessor constraint on a parent task whose duration is solely based on its rolled up child tasks. It just won't work. The only thing that occurs is the parent task's duration is set to one day starting today and the task for which I want to use as the successor always starts tomorrow.
How can I fix this without manually inputting a duration for my parent predecessor task, which will most likely change and be in conflict with the rolled up duration as the sub-tasks' timelines inevitably change?
(I really hope that makes sense)
Hey Samer Khalil, and welcome to the Community!
I've just raised a Support ticket for you, someone should be in contact with you soon. If you need anything else, be sure to let me know.