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.

Find more posts tagged with

Not planned

Status: Not planned

Comments

Permanently deleted user

Hi Gordon, thank you for posting this request! I wanted to share a similar suggestion about hiding dependent tasks in My Work, it would be great if you could add your vote to it all similar suggestions could be tracked in one place: Ordered active tasks based on dependency - My Work.

Larry Phung

This would be incredibly useful for my team too. +1

Keeley Reed

I have added this comment elsewhere, but figured it would fit here as well:

Two solutions could fix this discrepancy:

Tasks with open dependencies show up as “faded out” on dashboards so that teammates know that a task is in the pipeline for them, but also know not to start working on it until all dependencies have been closed (ie the task transitions from faded out to active).
Create a filter setting that allows for tasks with open dependencies to be hidden until all dependencies are complete.

Our team prefers the fade-out option, because they will know from a glance that they will need to start working on additional tasks, and can click into the dependent tasks to ask teammates if they need help completing the tasks, or can check on the status of those tasks to estimate when their task will become active.

Paul Snyder

Thanks, Keeley! I just noticed that "fade-out" feature, but wasn't sure if it was actually related to dependencies, so thank you for that confirmation!

Larry Phung

It would be ideal if there was a filter you could turn on and off to show or hide dependent tasks - similar to how you can filter tasks and only show what's due this week, this month, etc.

Julie Ricke

This is a great suggestion! It would be super to have this option available in reports as well.

Larry Phung

^^^This.

Daniel Jagelman

Agreed! We don't want workflow and report cluttered with tasks that are not ready to be worked on, this just buries the actual tasks ready for work. If this could be a simple filter would be great

Farhood KarimiSaber

Definitely could be helpful!! especially when you have tons of tasks to do. lack of this feature technically kills "My Work" tab and productivity.

Junpei Liang

Agree. Another option is to temporarily change the dependent tasks to non-editable/grey-out. That way, user can still see the task but can't make any changes until the initial task is completed.

Adele Tiblier

With so many dependencies, even the ability to mark something as BLOCKED so at a glance those with tasks that can't work on them know to move on to those that are actually available would be helpful.

We spend an inordinate amount of time messaging our PM and rooting through tasks that are blocked due to the dependencies that this would be hugely valuable to solve in some way.

Simon Williams

I'm currently undergoing a deployment with Wrike and this is going to be a hard sell for my team to not have available. I really don't understand how this has been asked for 2.5 years ago and still hasn't been released.

Karina Fluker

We REALLY need the ability to filter out tasks that aren't ready to be done. It's very frustrating for our team members looking at their dashboards with all their tasks - not sure which can be done yet and which can't. I like the idea of being able to either filter them out completely, or they are greyed out, or have a flag/icon on them of some sort to say it's still waiting on dependencies.

There are SEVERAL similar ideas posted about this specific thing across the wrike community, aside from this post:

/hc/en-us/community/posts/115000539069-FILTER-REQUEST-incomplete-tasks-for-which-all-predecessor-tasks-are-complete

/hc/en-us/community/posts/360000782289--Ready-for-you-filter

/hc/en-us/community/posts/115002630269-Dependent-tasks-if-only-they-activated-once-the-other-person-completed-them

/hc/en-us/community/posts/115000085065--Status-Not-Planned-Ordered-active-tasks-based-on-dependency-My-Work

/hc/en-us/community/posts/115000274229-More-control-with-dependencies-

This would be a HUGE help to our team and relieve a lot of stress.

Emily Lyon

We came back to Wrike after a year away trying different tools, thinking that by now dependencies MUST be implemented, since they are such a basic piece of PM. It's incredible frustrating for team to have to wade through their tasks - click INTO a task - and still have to click in and look at the dependency button to see if it's something they can actively work on. Really need a filter in dashboards that would exclude tasks that have an open dependency!

Steve Cross

Need this ASAP! Can we get an update on if this is in development or even on the roadmap?

Simon Williams

As I mentioned back in October, it's really surprising that this feature isn't available. I'm also surprised that it's been a further 4 months in addition to the first 2.5 years of this feature being requested and there hasn't been a response from a Wrike representative.

My team have now started working with Wrike. We're 3 days in and this is already creating confusion and clouding visibility. Confusion and a lack of visibility means time & energy are wasted... as are $$'s. Wrike is supposed to be saving $$'s, not costing.

Can the following please be answered asap:

When will there be a response from a Wrike representative on this request?
Why hasn't this been added as a feature in the roadmap already?
Will this be added to the roadmap at some point and if so, what questions to you have for the users who are requesting it?

Laura Boylan

We too would love to see this feature.. in the meantime, in the absence of built-in functionality, a solution is possible today with Wrike Integrate.

I posted a community recipe at https://www.workato.com/recipes/1089764 as an example.

This recipe assumes that all of the tasks waiting on dependencies to be completed have a Deferred status, which allows you to "hide" these tasks from most places in Wrike.

Whenever any task in the specified project/folder tree is completed, this recipe loops through that task's dependencies looking for successors, and activates any successor task where all of its predecessor tasks have been completed.

Note that this example recipe currently only works with Finish-to-Start dependencies. If your project uses other dependency types, the recipe would need to be adjusted accordingly.

Elizaveta Bogdanova

Hi everyone! I'm sorry the Community team hasn't replied here before! We have the voting system here, so once the post reaches 60 upvotes, it gets to a folder for the Product team where they add a status to the suggestion. At the same time, 60 upvotes is not a guarantee that the suggestion is going to be implemented, but the more votes it has, the more it is brought up during various discussions and roadmap planning.

Currently, I don't have any updates from the team, but this is very interesting feedback, I'll make sure to keep passing it to the team, even if it can't have a status yet.

Here's more info on the statuses and the voting system: /hc/en-us/community/posts/360014354593--Read-Me-Product-Feedback-forum-Guidelines-and-Statuses

And this is a post that explains how we work with Product feedback: /hc/en-us/community/posts/360019106654--Read-Me-What-happens-with-Product-Feedback-

Thanks a lot for your input here!

Sven Fagerstrom

Sixty up-votes before consideration sounds like the action lane for user-desired modifications; it seems this may be more appropriately characterized as a bug or error. The Wrike site says under Types of Dependencies "Finish to Start - Task B can't start before Task A is finished" - this seems to be not the case. Our experience is that Task B is actionable while Task A is incomplete. Individuals are being told they are late on action items they cannot action, as the prerequisites are incomplete. Please request management consider the possibility that this as an error rather than a convenience feature request.

Karina Fluker

In response to the 60 vote threshold, if you merge this suggestion with the many other suggestions about the same issue, there's well over 60 votes.

This post currently has 38.

Other suggestions about the same issue:

/hc/en-us/community/posts/115000539069-FILTER-REQUEST-incomplete-tasks-for-which-all-predecessor-tasks-are-complete

36 votes

/hc/en-us/community/posts/360000782289--Ready-for-you-filter

21 votes

/hc/en-us/community/posts/115002630269-Dependent-tasks-if-only-they-activated-once-the-other-person-completed-them

14 votes

/hc/en-us/community/posts/115000085065--Status-Not-Planned-Ordered-active-tasks-based-on-dependency-My-Work

86 votes

/hc/en-us/community/posts/115000274229-More-control-with-dependencies-

49 votes

That's 244 votes total.

Since we can't merge similar ideas, it's hard to actually see the combined total of what people need.

Permanently deleted user

Hey everyone! Thank you for all of the feedback here.

In regards to the 60 vote threshold, each thread has different ideas and suggestions, even if they seem similar. That is why generally threads are not merged together by the Product team.

I've passed on all of your feedback to the Product team. I don't have an update at the moment, but as soon as I do, I'll let you know.

Marcus Rosenthal

I bet if everyone who commented here told their entire team to upvote this we would hit the 60 vote threshold pretty quick. I agree this is very important. I'm trying to implement a Work Order system that really can only work if this feature is upgraded.

Wendy Pardo

We need this so badly (as do the so many other people that have requested this). We sometimes have 10 tasks per project (and we have 200 projects at all times) that people should NOT have to see tasks they can't start yet. Could you PLEASE ask for a filter option to grey out or filter tasks that are waiting on dependancies?

Thank you for getting us an update since this request was made back since 2017.

Wendy

VP of Operations

Elizaveta Bogdanova

Hello everyone! I'm sorry to let you know that for now, the team isn't planning to add this functionality. I will continue to pass on your feedback and regularly check for updates.

Emily Lyon

This has become a very big issue for our team - and now we're looking at other options because of the lack of working dependencies. It's such a basic PM tool feature, I can't believe this still isn't on the radar for the Wrike development team.

Elizaveta Bogdanova

Hi @Emily Lyon, thank you for reaching out! From your comments, I understand that you're relying on dependencies a lot in your team's work. Could you please tell me if you're using Gantt Charts to check out the dependencies? Also, last year, Wrike's Automation engine has been released, so it's now possible to automatically change the status of the next task in the dependency change to "Ready to be worked on" (you can use custom workflows to create such a status) once all predecessors are marked completed:

Please let me know if that helps in your case!

Erin Monday

There's 69 votes -- NICE.

Can we please get this in development? Due to the cost structure of the automation engine, my org has it disabled, and im sure we're not the only ones. A filter, or, logically -- a way for dependent tasks to not appear until the preceding task is done (perhaps tied to the finish to start, start to finish thing) -- would be helpful.

Elizaveta Bogdanova

Hi @Erin Monday, welcome to the Community 👋
Thanks a lot for supporting this idea! I'm passing your feedback to our Product team 👍 Although this post has the Not Planned status currently, please make sure to upvote the original post above if you haven't yet - the number of votes helps the team understand how popular the suggestion is. Here's more detail on that, but please let me know if you have any questions!
If you'd like to know what this Community has to offer, please check out our New to Community forum 🤗

Ama Nishi

Well... I am here today because yesterday my manager locked all prior years of QBs files because the subtasks populated her workspace even though the FS task was not completed. She is only assigned to the lock qbs sub-task and not the main task showing all of the subtasks. I then added her to the main task (so she can see the other tasks are not completed) which she requested to be removed from because she didn't want to see open tasks that did not need any action from her as it clutters her workspace. Has this feature been added? This would be supppper helpful. Now I have to go back and request that all the locked qb files be unlocked. This is a loss of efficiency for us. Thank you.

Elizaveta Bogdanova

Welcome to the Community, @Ama Nishi! 😊 Thanks so much for sharing your detailed feedback here, I'm passing it on to the team now!

Could you please take a look at a suggestion I posted above using Wrike's automation and let me know if that can be helpful in your case?