workflow transition request form
A major struggle my team is experiencing is the inability to get a single task from the beginning to the end of a workflow without a lot of manual effort. This would be easily resolved if we were able to insert automated request forms into the workflow.
For example, if I completed my work on a task, I'd like to be able to click "approve", or be able to move it into the next status of the workflow, and then have a short request form appear that asks me for certain information, and then it can append that data to the bottom of the task description before moving it to the next status.
I feel this would be monumentally helpful in keeping task descriptions organized and cleanly formatted, and will take the guess work out of "what information needs to go in this task".
Thank you for your consideration.
Steve
Being able to utilise request forms within a project or workflow would be a major help for us too.
The automation engine is great, but I'm really restricted in what benefits I can actually get out of it for the team, because rules can't be created for specific projects. Allowing users to create and submit request forms at any time from within a project/workflow (similar to how you can add new tasks / projects / folders), could help with that.
Hi @... - yes, custom fields are great. We really need the ability to have tasks auto-inherit custom field data from their project level though. Until then, we can't get much use out of custom fields on tasks, as it takes up too much time for our users to manually repeat the data, across multiple tasks within a project. At the moment, we use request forms to conditionally duplicate blueprints and populate custom field data at the same time.
https://help.wrike.com/hc/en-us/community/posts/1500000651082-Auto-Fill-values-in-Custom-Fields?page=1#community_comment_1500000586561
I will second the request! When a task is created from a request form it’s got a lot of great inputs, but most of the time not every piece of information is known. For example a completed version number or link to documentation etc. When the task is moved to final review stages for example testing or QC, that’s when the task should bring in a request form to have a user populate that information. A similar tool that does this effectively is salesforce workflows.
Another way to accomplish this would be to use a request form to append data to a task that exists already, rather than create a new task. You could even have a button on a task to ’add request form.’
Thanks, Noel Howell, Scott McIvor for taking the time to share your use cases. @Scott, thanks again for the explanation, all clear now 👍🏼
Hey everyone! 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