Successors column in Timeline View

I second this.  Having to visually trace the successor in the Gantt chart isn't effective.  Having a column would make Wrike more powerful.

I agree. It is hard to trace the logic with just predecessors, particularly when you've got a large programme.

I'm very surprised they don't support this.  Any person coming from MS Project is used to using this heavily to trace a dependency chain.  It is a very important and basic PM feature for complex projects.

I agree with this thread.  My projects have a fixed delivery date so being able to schedule tasks backwards to know when you should be starting would be a great feature.

Hi everyone, thanks a lot for suggesting and supporting! I'm checking with the team now and I'll get back to you as soon as possible! 

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

I so agree with this thread. Really need this for proper project planning and I am very surprised that this is not available in Wrike. This should be basic functionality to show the successors in a column of a table view. 

Hi again, everyone! I've checked with the team - they don't have this in their short-term plans, so please keep upvoting and sharing your use-cases, it really helps the team understand the popularity here. Any updates - I'll let you know. 

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

I agreed too, to be able to plan a project, tracing the decencies is essential. I think the successors column should be added to the views too.

Hi Masa -, welcome to the Community! 🤗

THank you for adding your support to this suggestion! As I mentioned above, the team isn't currently planing to work on this due to other priorities, but I'll let you know if that changes in the future 👍

Please let me know if I can help you with anything else!

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

I agree. In most programs I have worked on, there are always predecessor and successor and it is important to have both to identify dependencies. Not sure why it is difficult for wrike to implement this relatively simple feature considering this request was first made more than 4 years ago. 

Hi Asifbhai Vahora, welcome to the Community 👋

Thanks a lot for supporting this suggestion, I'm passing your feedback to the Product team.

If you'd like to know what this Community has to offer, please check out our New to Community forum 🙌

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

I asked for this in November 2020, earlier in this thread. To me this is the most important feature that is missing in Wrike, and it does not appear to be a priority for Wrike to implement. It is very important to be able to easily see both dependencies as columns in all views. I really hope that Wrike will implement this soon to provide as a significant improvement.

Hi Andy Sigrist, thank you for taking the time to bump this thread and share your thoughts. I've passed on your additional feedback to the team.

We'll be sure to let you know if there are any changes in relation to this suggestion👍🏼

Cansu Community Team at Wrike Wrike Product Manager Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

Cansu Wrike Team member Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

I see this thread goes back 4 years, but with no apparent progress from the Wrike team. I'm new to Wrike, so still feeling my way around, but, coming from an MS Project background, I see this is an important requirement. 

Hi Derry Holmes, welcome to the Community, and thank you for taking the time to share your feedback. 

Please allow me to share a little detail on how we process Product Feedback. We receive many great ideas on Community, and we pass on all feedback to our Product team. If you'd like to find out more, this article explains what happens after we receive Product feedback. 

We check with our team and assign a status after a thread receives more than 60 upvotes according to our Product Feedback Guidelines & Statuses. This suggestion at the moment needs more support. In the meantime, if there are any updates in relation to this suggestion, we'll be sure to update you here. Please let me know if you have any questions.

Cansu Community Team at Wrike Wrike Product Manager Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

Cansu Wrike Team member Aprenda sobre as funcionalidades e melhores práticas em Wrike com o nosso Treinamento Webinar Online

C'mon Wrike, why isn't this simple function not completed yet? 4 year?!

Joke! the Project Feedback Page doesn't have a search option. Where do I upvote this? 

Thanks a lot for your interest Juda Glick! You can upvote a suggestion under the main post in the thread:

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

I too can't believe this is not supported and visible by default in an exposed field.  

No one plans a project just based on predecessors.

We need to know who is dependent on our tasks and higher level PM's need to see the full chain of predecessors and successors.

Bump

Uplevel

Please!