Suppressing tasks with uncompleted dependencies
I wish that there was an option when setting up tasks with dependencies to make it so that those tasks do not show up on the assignee's dashboard until all predecessor tasks are completed. Our typical project has about 225 tasks. Many of them cannot be completed until prerequisite tasks are done, yet these unactionable tasks clog our inboxes and dashboards. I'd really like to make them disappear until someone can actually act on them.
Having a filter setting along the lines of "tasks where all prerequisite tasks are complete" would do it perfectly.
Hey David Harris, thank you for sharing this suggestion! It's been passed on to the Product team.
We have been asking for something like this for years. It is also a huge pain point for us. Maybe if we keep asking they will finally listen to us.
Welcome to the forums, Maryann Dupes! It's great you've reached out here on the Product Feedback forum, this is exactly the place to share your feedback 👍 Please make sure to upvote David's post - the number of votes helps the Product team assess the suggestion's popularity.
Lisa Community Team at Wrike Wrike Product Manager Conviértete en un experto en Wrike con Wrike Discover
Lisa Wrike Team member Conviértete en un experto en Wrike con Wrike Discover
Thanks Lisa. I believe that was the first thing I did, like I have in years past to other comments like this.
Thank you for that, Maryann Dupes! 🙂
Lisa Community Team at Wrike Wrike Product Manager Conviértete en un experto en Wrike con Wrike Discover
Lisa Wrike Team member Conviértete en un experto en Wrike con Wrike Discover
This is an older request, but quite valid and needed. We also need some way to better identify for our staff which tasks can be worked and which are blocked by incomplete dependencies. Suppressing these tasks would be ideal, but at the very least having a visual indicator that these tasks are blocked/cannot be started would be better than nothing.
EDIT: Found the answer here - https://help.wrike.com/hc/en-us/community/posts/360029451453. I was able to achieve my goal using Automation rules. I updated our blueprints to set all tasks in a dependent sequence to On Hold (Deferred status). Then, as predecessor dependencies are completed, the status auto-updates to To Do.
Thank you for sharing that Laura Boylan! I hope this solution will work for other users too 🙂
Lisa Community Team at Wrike Wrike Product Manager Conviértete en un experto en Wrike con Wrike Discover
Lisa Wrike Team member Conviértete en un experto en Wrike con Wrike Discover
It's not a solution, it's working around a solution that should be offered by Wrike years ago. Wrike was built quicker than fixing this HUGE issue.
Welcome to the Community Ruud Vlaar, and thank you for sharing your feedback! I'll now pass it on to our Product team.
Please let me know if there's anything else I can help you with.
Lisa Community Team at Wrike Wrike Product Manager Conviértete en un experto en Wrike con Wrike Discover
Lisa Wrike Team member Conviértete en un experto en Wrike con Wrike Discover
This week we made the decision to move on from Wrike, and it is primarily because this (fairly basic and common-sense) feature is not available. It is absolutely disgraceful that Wrike cannot do this and furthermore that it has not appeared even three years after we first asked for it. Frankly, few tears will be shed when we wave goodbye to Wrike in a few months.
Hi David Harris, we are really sorry to hear that! I understand that it can be disappointing to see some of the suggestions, especially those that were created a while back, like this one, not being developed in Wrike.
Wrike can't guarantee the implementation of all or even most of the suggestions. While our Product team would love to work on the majority of the fantastic suggestions our users share, it's not always feasible.
That being said, we truly value all the feedback we receive, and that's precisely why we have this forum. We carefully track and report on all data, as well as request status updates. Your ideas and concerns are regularly shared and discussed with the Product Managers at Wrike.
I hope this provides you with more context on how we work with feedback from the Community.
Again, we'll be sorry to see you go. If there's anything else I can assist you with, please let me know.
Lisa Community Team at Wrike Wrike Product Manager Conviértete en un experto en Wrike con Wrike Discover
Lisa Wrike Team member Conviértete en un experto en Wrike con Wrike Discover
Since I am leaving anyway, here are my other pet peeves. The way that Wrike stores comments on a project is nonsensical. Instead of attaching comments to tasks (which makes them hard to find later) my team has overwhelmingly asked for a "whiteboard" feature where all comments on a project can be found in sequential order. Second, the way that blueprints handle dates is maddening and not at all intuitive. Instead of some arbitrary "index date," It would me much better if a Wrike blueprint started at day "zero." If a project was to be finished in 120 days, then the final day should be 120. Making blueprints is a huge pain in the ass when you have to work from an index date.
Team consensus is that we collectively dislike Wrike and have seen little meaningful improvement since we signed on in 2019.