It would be extremely helpful to have a way to see a dependency chain when selecting a specific task on the gantt view. We have projects/folders with hundreds or thousands of tasks that are all interdependent. This results in many dependency chains "stacked" on top of each other. It is often difficult to trace out the various paths from a single task.
Current solutions that partially work:
- Cascasde Sorting - this shows the individual dependency chains in order but you lose context to the other tasks happening at the same time not in that dependency chain
- Successor/Predeccesor view on task - when you select an individual task, you are able to see a list of successors and predeccessors but again, out of context to other tasks and not interactive
- Highlighting selected dependency - when you click on a dependency on the gantt view, it highlights it blue; however, it only is possible to select the "top" dependency. If there are multiple coming off of a single task, you cannot select one "beneath" the top dependency
My reccomended solution (although interested to hear what others think) would be a way to select a task in the gantt view and have all of the dependencies (predeccessors and successors) and their paths highlight a specific color (or have all other tasks slightly grey out). This would visually show all dependency chains off of a task but still keep the tasks in context to all other tasks. Then you could select/traverse tasks in the chain easily and follow down a specfic path.
The images attached represent (in a very simple way) what I am trying to accomplish. This image shows the raw gantt view:
This image shows what I would want to highlight if I selected "1000 3 Frame Walls". The task is red, the predeccessors green, and the successors orange:
Then, if I were to select "1000 4 Install Floor Trusses", the highlighting would shift and I could then see the new dependencies highlighted, allowing me to traverse through the chain while seeing the other tasks occuring on the same dates:
I'd love to hear other feedback or see if this feature is possible to be added in (as it appears all of the data behind the scenes is already available and being used). Thanks!