Trouble with Request Forms, Blueprints, and Sub-Tasks
Hi all -
There's something I'm trying to accomplish and I seem to hit a roadblock with every method I try.
Our team has a Request Form that creates a Blueprint. The Blueprint has sub-tasks.
The trouble is that whatever the requester enters into the form, it only pushes that information through to the parent task of the Blueprint. This makes it cumbersome for me (the assignee on the sub-task) because I am constantly having to revisit the parent task for the details. It's even more irritating because my task is multi-tagged to another folder where all of my tasks of that type are saved, so when I visit the parent task, I'm leaving the folder.
I looked for a way to push form values through to the sub-tasks within the Request Form itself. Couldn't find anything.
I looked for an automation rule that would, upon submitting the main Request Form, create another Request Form for my task.
I also tried creating an automation rule where a subitem was duplicated if a new task was created, but I couldn't get it to work. It would create a task, but the subitem duplicated wasn't attached to it. It also didn't seem to work when I create a task with a Request Form. According to the automation documentation, "Once the rule is triggered, this action adds a subitem to the item that the rule applies to. The subitem is duplicated from an existing item."
Similarly, I looked for ways to have tiered forms (i.e. A Request Form within a Request Form). I think that would be a great feature.
Does anyone have a workaround for this? TIA!
Anna Wallace - Are either of these posts (post 1 or post 2) what you are trying to do, or a little bit similar?
Flowing custom field values between projects and tasks (or tasks and sub-tasks) would be immensely helpful, but it isn't possible today using Wrike's native tools.
Post 2 has a workato recipe to copy custom fields down through a task. That might be a workaround for you to explore.
My request isn't specific to custom fields, just the task description. But I suppose it could work! I see it's on the backburner, though.
Unfortunately we don't have Workato.
Appreciate the quick reply!
I have had the same issue! The automation rule isn't working as described in the documentation and as I saw demonstrated in some webinars/wrike videos. I am unfortunately manually copying/duplicating to create a Parent Task w/ a Child Task.
I like the idea of selectively copying the description from parent to child task (or project to task).
I have a project where that could be another way to communicate the information gathered on the form to the applicable task. Right now we're moving that information manually.
I have the same issue. Our implementation consultant didn't have a solution.
It's such a huge bug that a field that is populated at the Folder level can't trickle down to tasks/sub-items.
I understand that some values like "Status" can be different at the task and folder levels. But there are definitely a LOT that stay fixed from the parent (folder) level for the life of a project.
Hello Anna Wallace, thank you for creating this post. Please, let me know if you'd like me to move it to our Product Feeback forum so that other users can upvote your suggestion about copying descriptions from parent folders and adding them to their child items (specifically, to their description field) 👍
Hey @...! Let's do it. :)
Done Anna Wallace 🤗
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