Project Requests / Workflow Tasks
Hello,
I'm building a project request form that will create a project from a template.
I noticed that none of the description data from the form is copied to the subtasks of the template.
Is there a way to have this information flow through?
I would prefer if i can specify which information is copied to specific tasks and also have the subtasks be assigned to a user. Or even if there is an option to have a page create a project subtask.
Hi Rob, thanks for posting this here! Just to clarify: you'd like to map answers from certain questions to corresponding template subtasks, is that correct? I'd love to learn a bit more about the types of templates you use and what kinds of task/subtask structures they typically contain, this would be really helpful for understanding your use case. Looking forward to hearing from you!
We are building a Wrike Request from to help us organize a new employee task assignment.
What we are hoping is to have some sort of a drop down box similar to the 'Create Project From Template' field or the three lines beside the page title to allow the information collected for that page to be copied to the relevant task in the project template. By doing this, the assignee will already have the information they need to complete the task.
This should allow us to assign tasks without necessarily having to give the assignee visibility to the entire project mostly for privacy reasons.
Rob, thank you for following up, this is helpful!
My team frequently uses request forms to set up repeatable projects from a template, and it's been a very helpful feature. However, one thing that's missing is the ability to dynamically assign tasks to different users.
For example, I have a simple template set up for processing leads; I'd like to have the request form ask the requester to select their name from a dropdown, and dynamically assign one of the tasks to them so they can quickly and easily find it and track progress.
The logic exists to dynamically assign a project owner using a request form; could this be extended to dynamically assign tasks (either individually, or by assigning all unassigned tasks to "Person X")?
Larry Phung "This is your life and it's ending, one minute at a time."
I also see a value in this. Some of the templated projects we create from a form have tasks that should be default-assigned to the requestor - it would be great if we could map the field selections to the tasks. We also would like it to trigger a task for the project manager so they know there is a new project to manage (with a task telling them to set up the project and take the first step).
Hi Laura and Larry, thanks for your input and examples here. It really adds value to the internal discussion on this topic. Once I have any new information on this request, I'll be sure to share it here.
My team would even be happy if all of the data collected in the request form could be copied into each task from the template. We don't need the field to task mapping to be dynamic, but we do need the data collected to be in each task description, not the project or folder description.
Adding to Kyla's idea, it would be great if any custom field data would be copied to each tasks as well.
Just following up here. Where did we land on this?? I too have a need for project request data to flow to tasks, including custom fields. Is this on product roadmap maybe?
Hi, it's currently not on the short-term roadmap. Our Product Team have been made aware of this thread so please keep adding use-cases and votes and I'll update you all when I have more information 🙂
We have templated that are kicked off by a request form which include 3 (sub) projects and a handful of tasks. When the fields are selected in the request form, they are only mapped to the main/parent project, but we actually change this to a folder (it's an event) and need to field selections at the project level (for each of the channels we are marketing for the event). Today, we have to go into each field and update after the project is kicked off and add in all of the same campaign details - it would be a HUGE time-saver if these selections mapped down to the projects we need them in.
Any updates on this request? This is a huge barrier to adoption for our team. Without this feature, it is causing so much extra work, it isn't always worth the time. In addition, since the details aren't cascaded down, we can't accurately report on projects and tasks because there is too much missing data. There are 35+ votes for this from our team!