Parent/Child Tasks
I'm reaching out to this community to see if anyone has a solution for my use case. We use Wrike as an intake tool for partners to submit internal communication requests. Our production process routes requests to different team members to deploy each communication channel selected. But since a single task is created when a request is submitted, we have to manually duplicate the task for each communication channel selected.
Is there an Wrike solution that will allow us to separate a single parent task into multiple child tasks based on the communication channels selected? Has anyone else run across that use case?
Hi Charlie,
Have you tried setting up a multiselect question in the form (checkboxes) to ask the submitter which communication channel they'll need? If you do that, you can use conditional logic in the form, paired with blueprinted tasks, to create a separate task for each team associated with the request. We do something similar when a new project idea is submitted - we ask the submitter to think about the impacted teams and that creates a task for reaching out to each team:
You can also do additional logic to add the newly created subtask to that team's intake folder, assign it to someone, and set a particular status like this:
Would that all accomplish what you're trying to do with communications?
Hi Sarah,
Thank you so much for your response and for your patience in waiting for my response!
This is a great suggestion and I THINK it might work for me. To make sure I understand what you do, when your users submit a request and check the box that they need a list pulled from the Data Team, it adds a subtask "Submit Data Report Request Form."
Does that mean your users have to submit another form? And how do you pair the subtask creation with a blueprint? I'm slightly familiar with blueprints but have never used them, so I need to be walked through that process.
Thank you!
Hi Sarah, following up here. I had a couple other questions for you, let me know if you're still available.
Hi Charlie Vincent,
Here's the knowledgebase article on Blueprints: https://help.wrike.com/hc/en-us/articles/360013445394-Blueprints-in-Wrike
You would create blueprints of tasks, and then point the request form options to create additional subitems based on the user's selected options (See Dynamic Request forms here: https://help.wrike.com/hc/en-us/articles/115003404345-Dynamic-Request-Forms)
The blueprints in my example do point the user to submit another request form in order to submit work requests to another team. When I created the blueprinted tasks, I set them up with links to the appropriate request form in the task description so it's easy for the user to find. Wrike's request forms don't yet allow you to auto-redirect users to additional follow up request forms yet (not sure if this is on the roadmap or not Lisa - any ideas?).
Hey Sarah Dungey, I've found this Product Feedback thread on the topic, it would be great if you could support it: https://help.wrike.com/hc/en-us/community/posts/360051927573-Request-form-selection-launches-another-form
We don't have updates at the moment, but I'll keep it on my radar.
Lisa Community Team at Wrike Wrike Product Manager Wrike DiscoverでWrikeの専門家になりましょう
Lisa Wrike Team member Wrike DiscoverでWrikeの専門家になりましょう