Default Workflow needs to be able to be changed when tasks are already entered

Thanks for your post, Mark. I can see our Support Team were in touch by email and provided a quick solution for this so I'll just explain this below for other members who have this question too. 

 

 

However, you can update these tasks individually, or better yet, use mass editing to quickly update tasks that have the same Workflow status. See GIF below as an example and thanks again for your feedback here, it would great to hear an example (use case) of when this would be useful so our Product Team have a real-life example and can better understand the request.

 

The way Wrike currently works is that once you enable a specific custom workflow to the project/folder, all newly created tasks adopt the first active custom status of this workflow. All existing tasks keep the original or default workflow. Often we don’t identify that a custom workflow is necessary until after tasks are added. Wrike directs you to use mass editing to change each task status. In my case, this resulted in sending over 300 alerts to users that the status had changed when we were simply trying assign the appropriate workflow. Going forward, we’re training to determine the workflow and assign before adding tasks.

However, this is a very unfriendly design. I can’t imagine a scenario where a user would want to change the workflow for an entire project/folder but not impact existing tasks. My suggestion to Wrike would be to offer functionality that automatically updates the workflow assigned at the task level to the custom workflow. The task status if anything other than New (or the first active status), the task status would remain as is but the drop down would offer the custom workflow. At minimum, give users the option to change existing task workflow when changing at the project/folder level.