Feature Request / Idea- Workflows -> advanced statuses matching between workflows
It would be very nice to have an advanced option to match statuses between different workflows.
At the moment if you have a task in two projects with different workflows, in one of them task will appear in "Other tasks" section (board view). If there would be an option to say that Status X in Workflow A is matched with Status Y in Workflow B (obviously in the same state i.e. ACTIVE) then moving the task in one of the workflows to different status would move it also in the second workflow. One status of Workflow A could be matched into N statuses of Workload B and N statuses of A into one status of B etc.
Status A of Workflow B could me matched to N workflows etc.
This way you could manage tasks in different workflow i.e. simple for support and more advanced one for developers (more statuses).
Example:
Support Workflow
(S1) New
(S2) In-progress
(S3) Completed
Developers workflow
(D1) New
(D2) In-progress
(D3) Testing
(D4) Ready to production
(D5) Completed
S1 <->D1
S2 <-> D2, D3, D4
S3 <-> D5
etc...
Obviously it would be nice to mach statuses of one workflow to statuses of N workflows.
Could you create the task twice one for each different workflows role in the task?
Cool automation idea Christopher, our team loves hearing ways to automate. However, this is a deep workspace request and is not likely to be added to the roadmap soon. If I hear differently, I'll be sure to update you here.
For now, Zil's idea of creating two tasks for each might work for you. You can use the permalink and paste it in each task for reference. The downside to this; you're duplicating tasks. However using this same logic, you can say you're currently duplicating Workflows by having one for Support and Devs.
I wonder if Support could use the same workflow as the developers? There are only two statuses in that workflow (D3 and D4)that support don't need, otherwise, they're identical. I always recommend creating the least amount of workflows as possible in your company.
Instead, think of Statuses which could be applied to as many teams as possible. Not always possible, but that should be the goal - fewer workflows, more clarity for everyone. This way when tasks are shared across different teams, the Workflow used isn't really specific to one of the teams and the other team involved are not querying what each Status actual means etc.
Love to hear your thoughts 🙂
Hey folks! One of Wrike's Product Teams is currently conducting research in relation to the process creation experience in Wrike. Please check out this post for more info; it looks like if you've supported this suggestion here, this topic may interest you. If you'd like to participate in this research, please leave a comment in this thread 🙂
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