Wrike Automation Engine

Automation Engine Feedback:

First, I LOVE the possibilities.

A few things that would help my team:

  • I hear this is coming, but automated status changes when all predecessors are marked a specific status. For example, we have a webhook now that turns all successors to In Progress when the predecessor is marked Complete or Cancelled. I hope to replace that with the Automation Engine one day.
  • The rule for "If task status doesn’t change in" is nearly amazing, however I wish there was more customization over the notification frequency in terms of recurrence. I would like to have the option to say, "Notify me if In Progress hasn't changed in 15 calendar days" once, rather than continuously each day until it changes.
5
6件のコメント
Spot On Innovative Approach Stellar Advice
Avatar

Great features...but a few tweaks would be very helpful.

0
コメントアクション Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hey guys, thanks so much for your feedback! 🙂

As this functionality has just been released, the team is very eager to hear what you think and they are keeping a very close eye. 

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

1
コメントアクション Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi Lisa,

Sorry for confusion on my end, I was commenting to you on another thread as well.

This is amazing! I do have one comment about this which prevents us from using it over our webhook. I have a suggestion for the logic on Wrike's end.

Current Scenario:

Scenario: Apply to tasks-->if all predecessor statuses are Completed or Cancelled, change task status to In Progress.

  • Project 1 is kicked off. Because task 3 test is optional, it is cancelled unless an assignee requests it. In this case, task 3 is never requested and thus intended to always be a cancelled task.
  • 1 test is marked complete and 2 test bumps to In progress
  • 2 test is marked complete and 3 test bumps to In progress, but it was supposed to remain cancelled.

I want the engine to recognize the exception that 3 test should have been skipped and left cancelled rather than bumped to In Progress so that 4 test can be updated to In progress when test 2 was marked complete. I've tested it out and the logic gets wonky with multiple dependencies and bumps both test 3 and test 4 to In Progress.

 

Solution Scenario:

My initial thoughts for a solution is: an element of "exception", "unless", or "only when" logic. 

Apply when task is "New"-->if all predecessor statuses are "Completed" or "Cancelled", change task status to "In Progress".
This means that unless the task is currently marked as a specific status, the task will be ignored and it won't apply the predecessor rule logic.

4
コメントアクション Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Lindsey Walters I've already passed on your feedback here from a different thread, thanks a lot for posting 🙌

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

0
コメントアクション Permalink
Spot On Innovative Approach Stellar Advice
Avatar

I agree with Lindsey above. The main feature I find lacking is that you can't add exceptions. For example, I built an automation that marks following tasks as new when all preceding tasks are complete. This is due to a separate issue within Wrike, which is that users were being notified about tasks that they could not yet complete due to dependencies not being enforced. So, all tasks in our system start with a status of "Dependencies not met" (which we created) and then get moved to "New" status by the bot when their dependencies are completed. However, if users do not correctly mark their predecessors as done, but then mark the following tasks as done, when I go through to do project clean-up, the bot changes tasks that are marked complete back to new. Which is very confusing to the users. 

An ability to add an exception such as change status to new UNLESS it's completed or cancelled would solve this problem for us. 

 

Here's a link to the discussion around the dependencies issue: https://help.wrike.com/hc/en-us/community/posts/115000274229--Status-Backburner-More-control-with-dependencies-

0
コメントアクション Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Thank you for sharing your feedback and use-case, Kathleen Paluso! Our Product team is keeping a very close eye 🙂

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

0
コメントアクション Permalink

Folllowing List for Post: Wrike Automation Engine
[this list is visible for admins and agents only]

トップ
Didn’t find what you were looking for? Write new post