Successors column in Timeline View

Would be great to have the ability to show a "Successors" column as well as a "Predecessors." You can see it on the Gantt, but having it on the table view makes the Timeline view that much more functional, particularly for long chains of dependencies.

Find more posts tagged with

Not planned

Status: Not planned

Comments

Jason Shechter

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

Tessa Flaws

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

Rich Warwick

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.

Chris Schenk

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.

Elizaveta Bogdanova

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!

Andy Sigrist

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.

Elizaveta Bogdanova

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.

Masa -

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.

Elizaveta Bogdanova

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!

Asifbhai Vahora

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.

Elizaveta Bogdanova

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 🙌

Andy Sigrist

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.

Cansu Yetisgin

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👍🏼

Derry Holmes

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.

Cansu Yetisgin

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.

Juda Glick

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

Juda Glick

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

Elizaveta Bogdanova

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

Chip Linthicum Jr

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!

Elizaveta Bogdanova

Thank you for supporting this suggestion @Chip Linthicum Jr. We don't have an update for it at the moment, but we continue sharing all new feedback from this thread with our Product team.

Mikaël Thiesse

When entering the detail view of a task, you can see the fields "predecessors" and also "successors". So the field "successor" exist and it must not be so difficult to just add the "successor" column I guess...

Juan Muttoni

Hi Mikaël Thiesse, thank you for your comment. The "Predecessors" column is currently available in the New Table view:

Is this what you were looking for?

Mikaël Thiesse

Hi Juan,

thanks but yes i'm aware of the predecessor column. But the successor column is also very important/practical.

Juan Muttoni

Hi @Mikaël Thiesse, thank you for your reply. We will keep you updated in case there are any changes regarding this option 👍

Cathy Cowans

Yes please add the ability to see the successors in a column just like the predecessors! Any possibility of this becoming a thing?

Elizaveta Bogdanova

Hi @Cathy Cowans, welcome to the Community 👋

Successors aren't currently planned for the table portion of Gantt Chart, but we've informed the respective Product team of your interest and support of this feature. We'll share any news here if there's an update in the future.

Apologies for the late reply!

Ross Ashley

I really support this feature and it looks like there is enough votes to have this considered for implementation.

Effective schedule building means that all tasks must have predecessors and successors. If not, you may end up with an incorrect critical path (the task isn't connected anywhere and so cannot potentially drive the end date) and/or you may not understand how much float you have in that task if it is delayed.

As this feature is readily available for predecessors, would it be significant effort from the Wrike team to add the same feature for successors? The value to project teams would be very high.

Basudha Sakshyarika

Hello @Ross Ashley! Thank you for your feedback. 👍🏽

Since this post received 60+ votes, I've checked with the Product team and added the Backburner status here. This means that the team is interested, but it has not been added to the roadmap yet. I'll get back to you here when I have an update on this.

Thanks 🙂

Ross Ashley

@Basudha Sakshyarika thanks for the feedback. As others have said, it is the same feature that is currently in place for predecessors. Right now it's causing a lot of manual effort for each Project Manager to sift through missing successors but we have an automatic report listing tasks without predecessors.

Making this change will drastically improve efficiency, scalability and robustness of plans.

When do you think you'll be in a position to advise if this can be added to the roadmap for feature implementation?

Basudha Sakshyarika

Thank you for your comment, @Ross Ashley. 🙋🏻‍♀️

I agree and can see that adding the successor would be helpful in improving efficiency and scalability. As I mentioned earlier, the team is interested in this suggestion; however, there are no clear plans as of yet. I will revisit this in the coming months, check with the responsible team, and share updates. Thank you! 😊