Successor task information not showing on table view
When we select Predecessor info to be displayed on the table/Gantt view of a specific project, the information actually shown in the Predecessor column is both predecessor and successor task IDs separated by a comma if there are multiple dependencies. Trying to follow the dependency lines from task to task in a complex Gantt is not efficient.
To confirm which is which, user has to go into the specific task and select "dependencies" where it actually shows all Predecessor and Successor tasks.
For efficiency, recommend that the user is able to select either/both Predecessor and Successor which would show up in separate columns in the table/Gantt view, therefore allowing the user to see this info without having to go into each task separately to confirm.
Hi TODD SAVAGE, welcome to the Community and thank you for taking the time to share your feedback. I'm passing it on to our Product team🙌🏼
I'm not seeing this, has this been fixed now?
I'm only seeing the predecessor information for tasks that are in the same project or sub-project that is presently being view.
Should this comment/ticket be marked as closed/fixed now?
This has not been fixed. I have not received an update from anyone on the status of this.
Hey folks! We don't have an update for this suggestion at the moment, but please rest assured your feedback has been passed on to the responsible Product team.
Lisa Community Team at Wrike Wrike Product Manager Torne-se um especialista em Wrike com o Wrike Discover
Lisa Wrike Team member Torne-se um especialista em Wrike com o Wrike Discover
This is very basic requirement, I am not sure why it is taking such a long time to implement.
I want this feature too. It's years later.
Rohan V Community Team at Wrike Wrike Product Manager Torne-se um especialista em Wrike com o Wrike Discover
Rohan V Wrike Team member Torne-se um especialista em Wrike com o Wrike Discover
I'll echo this. It's really helpful to have a successors column as well to identify tasks that are endpoints (especially unintentionally). Most other PM tools I've used have this. It's also helpful while building out a schedule and thinking "what happens after this work is complete," rather than just working backwards.
Hi Sean Trimby, thanks so much for sharing your feedback here 🙏 We’ll share your comment with the relevant team for them to look into.
Rohan V Community Team at Wrike Wrike Product Manager Torne-se um especialista em Wrike com o Wrike Discover
Rohan V Wrike Team member Torne-se um especialista em Wrike com o Wrike Discover