[Status: Not planned] Hide dependent tasks until initial tasks are complete
We frequently have tasks that have starts dependent on other tasks being completed. Right now the due date changes on all tasks in a chain if the first one is moved, but it still clutters up our dashboards with tasks that can't be completed yet. We'd love if we could hide these tasks until the initial task is complete.
Hi Lisa.
I did read your suggestion above and it's not really going to work for us. We are a small office (less than 50 employees), I have set up to have those sub-tasks with a start date way later and have the status color changed to red. I will manually have to monitor my subtasks and re-date and re color my manager's subtasks when it is ready for her to work on. I colored it red so if it does pop-up, she will inquire why it is red and not start on the task. I have also updated her dashboard to only show tasks for the current week where as I had it set up to show all active tasks (future tasks as well). We have columns running from active, green, yellow, red and deferred.
I think this will be a good fix until there is a better solution. I couldn't imagine monitoring/managing these tasks if we were a large office. I am currently motivated to monitor my "lock QBs" tasks as it directly affects me and my ability to do my work.
I really hope and pray that in the NEAR future this ability will be added.
Thanks a lot for your detailed reply, Ama Nishi, that's really helpful!
We'll let you know if we have an update from the Product team on this 👍
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'm here for the fade out idea!!! I would love this so much, and I know my team would love it. One big bit of feedback that I get a lot is that sometimes they don't know when something is ready for them, so having that visual for them would be incredible. What is the status on this with the Product Team?
Hi Brittany Stringer! Thank you for supporting this suggestion.
The status here remains "Not Planned" at the moment, but I'm passing your feedback to the team 👍
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
Have to agree here with what was said above - that a Finish-Start dependency is able to be worked on and shows up in to-do's as ready for action even though the predecessor task is not yet finished should be considered a bug that needs to be squashed ASAP, not a feature!
Otherwise what is the point of this kind of dependency for the end user responsible for the task(s) except to have a pretty visual and some automatic date changing when dragging it around a Gantt Chart? Clutter = Inefficiency, isn't that the whole point of Wrike's new lightspeed interface?!
Honestly struggling to believe that requests to solve this issue, with literally HUNDREDS of cumulative upvotes across several basically identical threads (I just read them all looking and hoping for a reply somewhere that this issue had been fixed), is apparently still not even on a roadmap after 5 YEARS of requests.
That's 5 YEARS of users being frustrated by a needlessly cluttered to-do. Much sad, Wrike ☹️
I'm sorry to hear you're disappointed at the lack of this functionality in Wrike, Angela Kennewell. Although I don't have an update for this at the moment, please rest assured that all feedback is being reported to our Product team, and if we have any updates on this in the future, we will 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
Was this ever completed? If so, where can I find information on how to accomplish this? Thanks!
This is definitely better than nothing but, unfortunately, this workaround means that almost every single task we schedule would count toward our monthly action allowance. For context, we currently have 350 active tasks alone. Just to automate this, have parent task status update to In Progress if a subtask starts work, and have start/due date reminders would almost immediately eat up our half of the allowance assuming each only runs once. This doesn't really feel acceptable for what should be a pretty basic project management feature. Additionally, the rule is only acting in a "forward" fashion - meaning if for some reason something gets marked completed by accident, all subsequent statuses won't revert back on reverting the predecessor status without some sort of additional automation.
We appreciate your feedback Travis Balthes, thank you for sharing it! I'll now send it on to the responsible Product team at Wrike 👍
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