What can we help you with?

e.g. Gantt chart, Creating tasks, Sharing folders

Blog

[Status: Backburner ⌛️] Automatic Task Status Changed on Dependency completion

64 comments

  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Chance Callahan Burgess

    Up-voting this feature request. Would be very helpful for us!

    Is this helpful? 4
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Mitch Simpson

    Tagging on my +1 as well. This would be key for us to manage our project planning process. We manage hundreds of concurrent, templated projects and having tasks become active automatically would save a lot of time spent with manual effort!

    Is this helpful? 5
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Robert Bridgham

    This is an important step and seems easy to implement.  Wrike already posts a note in the stream when the task is complete, it is aware of dependencies and predecessors and should easily be able to set the next task to a canned status even if we can't customize it.  We move tasks from "New" to "Ready" (meaning that task is open for work) to "In Progress" (Meaning the task is being worked) to "Complete" (meaning the task is done).  Having a predecessor setting the next subsequent task from New to Ready makes a ton of sense and has a lot of support from the customer community!  

    Is this helpful? 3
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Kevin Dow

    We really need these feature as well.  We have several large 30+ task projects that are not time dependent but task dependent.  The  next task should only show as assigned/active once the predecessor task is completed.   This would help with the dashboard/reporting function as we can then simply filter by active tasks.

     

    Any further word on this feature?

     

    Is this helpful? 2
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Lisa

    Hi @Everyone, thanks for your continued input here 🙂 All your feedback is passed to our Product team, and upvotes of the original suggestion help them assess its popularity among Wrike users. For now, I don't have an update to share with you, but I'll get back to you when I have news. Once the suggestion hits 60 votes (so close!), we'll add one of the Product Feedback statuses to it. 

    Lisa Community Team at Wrike 🌎Discover... Wrike Discover and become a Wrike expert. Click here to get started

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Soraya Jung

    @Lisa looks like we're at +62 votes. Any chance we can get a Product Feedback Status on this?

    We REALLY need this feature as well, I completely agree with the comments/request that Ruby and Rober have described. We're 100 users now and work across 6 departments. The more we can get automated the better, I would assume that is the point of a project management software after all! ;)

    Thank you!

    Is this helpful? 2
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Stephen

    @all, I've added investigating to this post now. The team are looking into automation around tasks and will review the possibility of this request too.

    Its part of a larger functionality investigation as this affects many other functions within the Workspace, so it might be a few weeks before I have any further information.

    For anyone wondering what these statuses are all about, read me 👍

    Stephen Community Team at Wrike 🌎Discover... Wrike Discover and become a Wrike expert. Click here to get started

    Is this helpful? 1
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Patrick Danielczyk

    Howdy! I see that the status says "Now in Wrike Labs" but I do not see it there. The "Approvals in Tasks" is now there, but I think that is different than what this thread is talking about. Currently, many of our workflows start at "Incoming Job", and then whomever competes the first dependent task changes the status of the second dependent task to "Ready for Production" (or the related status for that department). I thought this thread was about automating that step. Am I wrong?

    Is this helpful? 1
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Mitch Simpson

    Agreed with Patrick. Looking at Stephen's previous note, it's likely that task approvals are step 1, then step 2 is automating based on dependencies? I would personally see this as the most logical way forward.

    Is this helpful? 1
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Lisa

    Hey guys, thanks for adding to this thread.

    Limited transitions for Workflows have been publicly released and removed from Labs. They are now available for Business and Enterprise accounts that enabled it from Labs earlier. It will be enabled in the coming days for those who haven't enabled it from Labs 🎉

    I'm removing the "(Now in Wrike Labs)" from the post title, but I believe I shouldn't mark it as "Launched". What do you think? 

    Lisa Community Team at Wrike 🌎Discover... Wrike Discover and become a Wrike expert. Click here to get started

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Patrick Danielczyk

    Howdy, Lisa! I think Limited transitions for Workflows is an entirely different thing than this thread is talking about. Those transitions, if I'm not mistaken, are all in the same task. This request is for a status change in one task causing a status change in a dependent, second task. I may be wrong, but that's my understanding.

    Is this helpful? 2
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Mitch Simpson

    100% what Patrick says. I see it as the following example:

     

    You have two tasks:

    TASK 1 ; Status: Not Started

    TASK 2 ; Status: Pending (Dependent on Task 1)

     

    When TASK 1 is changed from Not Started to Completed, it should then change TASK 2 from Pending to Not Started, or similar.

    My feeling is that it should basically change the second task from a pending/on hold status to active, so that the team knows that it can be worked on/actioned.

    Is this helpful? 6
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Scott Henderson

    Agree w Patrick and Mitch. Limited Transitions for Workflows is a great feature but a separate issue and does not address what this thread is about.

    Scott Henderson Arizona Community Foundation azfoundation.org

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Lisa

    Thanks a lot for your opinions here, guys 🙂 I agree with you, so I'll get back here when I have updates on the original suggestion.

    Have a great day!

    Lisa Community Team at Wrike 🌎Discover... Wrike Discover and become a Wrike expert. Click here to get started

    Is this helpful? 1
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Al Sape

    Fully agree this would give a great benefit, another piece of automation that could add some ninja speed, to use the cliche, to Organizing work when initially entering into Wrike

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Soraya Jung

    We're looking for the exact same feature that Patrick, Mitch, and Scott are referring to. It would save us a lot of time, and avoid a lot of manual error, if a task's status would be automatically triggered by a dependency.

    Looking forward to an update from Wrike on where their investigation is at on this. Thank you!

    Is this helpful? 1
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Greg Honeybourne

    We are looking for this as well as my team has many pre-assigned tasks that look all the same unless the status can be changed to something else when it is ready. 

    Seems like a simple fix but this chain has been going on for 2+ years now??? Yikes.

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Vicki Frame

    We would also like this feature. I was trying to set it up just now for my team and could not understand how this is not already a feature.

    Changing the status of an active task to include an additional assignee isn't helpful for us. We try to obey the "one task, one assignee" rule.

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Matt Horne

    This is something that's definitely missing and oddly so since it just makes sense to happen automatically.

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Lisa

    Hi everyone, thanks a lot for your support here!

    The team reviewed and investigated and for now, the suggestion is not added to the short-term roadmap. However, I'll keep passing your feedback to the team and I'll let you know when the status is updated. 

    Lisa Community Team at Wrike 🌎Discover... Wrike Discover and become a Wrike expert. Click here to get started

    Is this helpful? 1
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Joshua Balentine

    If the goal is to show when a task is held back because of a predecessor or ready to go when it finishes, changing the status seems a bit complicated. How would you configure it or disable it when you don't want it to happen?

    I made a post asking to show if the task is blocked by a predecessor on the task lists and details views. That visibility along with the notification that's already in place to ping the assignee when all predecessors are finished should accomplish the same goal as this post in a simpler manner.

    Improve Dependency Visibility

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Mikhalina Dombrovskaya

    This would be a great help to out team, we spend a lot of time manually updating tasks to 'active' which could be automated using the proposed feature.

    Is this helpful? 1
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Laith Marmash

    Looking through this thread, I'm shocked that this still hasn't been developed yet. It's a pretty simple feature! Come on Wrike developers! 

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Luis Aguilera

    Thanks a lot for posting your comments related to this issue.... this is so important for taking the decision to buy this service.... definitively, you have the customers waiting from 2 years with no real improvement.

     

    Fortunately, I'm using the trial period... so, thanks a lot, but I will continuing using my current service.

     

     

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Elizabeth Bayer

    We absolutely need this. Our company deals with rapid change workflows, and while it is nice to get a notification, the status has to change to make our workflow better. 

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Jason Tseng

    +1 This is a key and critical feature for effective task management within a project.

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Lisa

    Hi again everyone! I've checked with the team again, and there are no updates for now! I totally understand the importance of this suggestion, personally, it would save me a lot of time too.

    As you can imagine, we receive a lot of feedback on the Community, some suggestions get implemented, some are not. At the same time, please rest assured that all the suggestions are passed on to the team. The team review them constantly, and a lot of released features are based on the use-cases that you provide. Being one of our feedback channels, the Community helps drive our product forward, that's for sure. Thank you again for providing your feedback here!

    I'll get back to you as soon as I have an update for you. 

    Lisa Community Team at Wrike 🌎Discover... Wrike Discover and become a Wrike expert. Click here to get started

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Al Sape

    Hi Lisa

    It's interesting to see a flurry of activity from you guys the last few days.  But I have to note that as usual, you guys are up to your typical Modus Operandi, and this is one of the biggest reasons I have moved on from Wrike.  Yes, paid $2700 for my team in the fall - a year in advance, of which I had no choice due to your archaic pricing policy.  But Wrike disappointed within a month, and I've swallowed the investment and moved on.

    I am subscribed to about 15 threads, most of which are about basic functionality I found lacking in Wrike.  To my chagrin, there is no movement from you guys on about any of them.  Conveniently I don't see you or your team getting into some of these particularly relevant threads.  I'm going to post them right after this so this post doesn't get flagged because of its links.

    You can see frustration in these posts (see below), and I concur with my fellow Wrike users in both cases.

    I have mentioned this in the community in the past, but for your easy reference, I will repeat what I see as some of the issues with the way you guys interact here, and your Roadmap management in general:

    - you have a ridiculous "60 vote" policy, while who knows how many of your thousands of users are even aware of these requests in the first place for a request to even get votes? How did you come up with that number?  And how many requests in here with 60+ votes are years old now?  This policy is a nice way to blow off relevant requests you can't address

    - you release functionality, like "my work," which is nowhere to be seen here in the community, and I agree with some of my colleagues in here that this is a pretty useless improvement in the first place.  Where is your information about how you choose stuff for your roadmap?

    - a ton of requests sit in here years.  And you guys come in from time to time with the same, stale responses:

    "Product will get to it". - who's Product??  You are one company.  I could not imagine passing the buck this way with paying users in my business, this is pretentious and disrespectful to your audience.

    "No updates for now" - that's a nice way to say "we'll get to it when we want to, if we want to."  I can't believe you continue to repost the same comment again and again.  Makes me wonder if part of your job description is to figure out the same way to diplomatically repeat the same message in as many different wordings as possible.  Sorry if that's harsh, but this is the truth.

    "We appreciate the feedback" etc., yet your frequency of posting is rare, at times a year or more will go by with no response from you guys

    Generally you have a great way to avoid most of the key questions in here, like what is the true limitation technically that you frequently fall back on, what really is the product team working on, etc.

    In one of the threads below, a fellow colleague suggests you will continue to hemorrhage users with this poor attention to Product Updates.  I'm one of them.  This is probably one of my last posts in here, after starting out very enthusiastically when I got involved with Wrike.  I now feel burned, and I am using another tool which is much superior than Wrike for starters, and run by a team that listens to feedback from users, and builds around that, so it can keep those users!

     

     

    Is this helpful? 2
    Comment actions Permalink
  • Is this helpful? 0
    Comment actions Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    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.

    Is this helpful? 0
    Comment actions Permalink

Please sign in to leave a comment.

Folllowing List for Post: [Status: Backburner ⌛️] Automatic Task Status Changed on Dependency completion
[this list is visible for admins and agents only]

Community

Welcome 🖖

Hi there! 🙂 Want to become a black belt Wrike Ninja? Here's how to earn a Wrike badge

Welcome 🖖 Have you checked out this week's Release Notes yet?

Hey! 👋 Curious about something? Visit How To to search and ask the Community for answers.

Welcome! 👋 Figured out a good tip or trick? Share it in Best Practices.

Want to connect your existing software to Wrike? Learn and ask how in the API section.