[Status: Backburner ⌛️] Include Subtask Details with Dynamic Request Forms

We would also find this really useful...

Hey Soraya Jung and Annie Briggs, apologies for the delay in response here.

Thank you for sharing your interest in this suggestion! I don't have an update for you at the moment, but if there is any new information in relation to this idea, I'll be sure to let you know. If you need anything else in the meantime, feel free to reach out at any time.

Upvoted! We have the same need. We use request forms to populate all of our common tasks from templates. We'd really like the ability to modify the descriptions, assignees, dates, and titles of subtasks - or even add sub-subtasks if possible. I think Soraya's suggestion to have a second page that applies answers to a subtask would be fantastic.

Thank you for sharing your thoughts Jessie Ostrander! Please make sure to upvote Soraya's suggestion, the number of votes helps our team understand the popularity of the suggested functionality 👍

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

We would also find this extremely helpful as we are currently having to manually copy the information from the project into the tasks.

Hi again! I'd like to had some follow up on this request.

2 years later, and we still have a huge need for this functionality specifically in external forms that our clients or customers are filling in.

If the logic wasn't applied to subtasks, then simply some sort of logic that allows admins to choose if a form page creates a new task (and all the responses on that page map to this new task) would also be a great alternative.

yes 100% would use this!

Hi Soraya Jung, thank you for bumping this one and sharing your additional feedback. The Product team is aware of your feedback here, and I'll make sure to keep the thread updated 🙋🏻‍♀️

Great idea!

Hey everyone! As this post has reached the 60 upvotes threshold, we've asked our Product team to provide a status and an update here.

They aren't currently planning to research this, but they may reconsider in the second half of 2022. For that reason, we set the status here as Backburner and we'll let you know when we have any further updates.

Thanks a lot for voting and sharing your feedback here 🤗

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

Has there been any movement on this? Our team would love this feature so we can make our forms more tailored to our needs.

Hi Robyn Gilbey, welcome to the Community and thank you for checking in. There are no updates for the moment, in case there is a change we'll be sure to let you know here🙋🏻‍♀️

I would also find this helpful. I'm currently trying to build out a request form that creates a task with 2 subtasks. The subtasks have different simultaneous work streams, one for copywriting and the other for graphics. When my team fills out the request form, I really need the information pertaining to the graphics portion to go into the graphics sub task, and the information regarding the copy portion to go into the copy subtask. Currently, all the info they put into the request form only populates the main task, which means they will manually need to copy content over into the correct subtask, which isn't efficient at all. Any workarounds currently?

Hi Michelle Sheppard, I'm afraid this is not possible for the time being, I'm passing on your feedback to our Product team. 

This is critical for the functionality for our most frequently used request form. 

Would  really like to see this being bumped to a future sprint 

Thank you for supporting this idea here, folks. We will let you know if we have an update in the future 👍

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

Hey Lisa,

As it is a backburner - is the team made any decission yet? This functionallity is also needed on our use case.

Needed here too, hoping for an update on this soon!

Hi everyone, thank you for supporting this suggestion and checking in here continuously. We have checked with the team and it's in their plans to further look into this suggestion within this year. We'll be sure to update you here when we have more information 🙋🏻‍♀️

I strongly encourage to include this feature in the request forms. In some occasions I found it very helpful to detail the subtasks directly from the request form, instead of having to manually fill in the information afterwards. This feature would avoid mistakes and ensure that all the relevant information is filled into the subtask. It would indeed make the request forms a much more powerful tool. 

Hi Carolina Pinto Correia, welcome to the Community! Thank you for supporting this idea, I'm checking for updates about this suggestion with the Product Team 👍 

In the meantime, please feel free to visit our New to Community forum to get the most out of your experience with our Community 🙂

Hello everyone 🙂 Even though our Product Team is interested in this suggestion, I'm afraid that its implementation has been postponed. I understand this is not the news you were expecting, but please rest assured that we will share more updates with you as soon as we are informed about them 👍

Thank you for supporting this suggestion and for your understanding! If you have any additional questions, I'm here to help.

This would be a great feature. I currently have a form in which the user can submit multiple entries on one form. The use case is that senior leaders conduct conversations with employee groups. During the conversation, multiple topics can be discussed, having multiple themes, and resulting in multiple action items. I'd like them to be able to submit one form with the conversation, all of the conversation topic details, and corresponding actions to be completed all with one form. There are certain fields that are identical, and others that are unique. For instance, the leader and audience details are the same, but multiple topics can be discussed (having different themes and resulting actions/tasks), and we want to collect the details about all of the topics discussed during the same conversation, as well all of actions so that we can assign and track those actions. The actions can have different assignees.

The problem is that if the custom fields are the same, they end up overwriting each other. While you're able to create multiple custom fields, it's not an ideal solution because the data is being sent to a folder, and the folder's data is being used in an Analytics dashboard to give us an overview of what was discussed within the company, and which actions were captured (including who's responsible for completing those actions). We want to track that progress.

I've been able to implement a workaround by creating multiple custom fields with the same name, and multiple custom items that only contain the information from specified fields. For example, I started with theme 1, theme 2, theme 3, theme 4. I then built out custom item 1, custom item 2, custom item 3, custom item 4. I then removed the number from the name of the custom field resulting in theme, theme, theme, theme. A form was built that creates a project (conversation) and adds subtasks (conversation topics and actions) using the custom task item types.

This would work perfectly, except there's still the manual portion of copying the parent project data to the subtasks within the project. I upvoted an existing request to have subtasks inherit parent project custom field values. If the subtasks could inherent the custom field values from the parent project, this would work perfectly and completely automate the form since the Analytics board is working on Task Custom Field Name (Note Name(ID)). 

The ability to have the form create the project and multiple subtasks with custom fields having unique values (and not having 4 of each custom field with the same name, and not having to create the custom item types each containing data from one of the 4 custom fields with the same name) would be a better more streamlined solution. The workaround was extremely labor intensive and time consuming. Just adding my thoughts, workaround, and use case.

Please continue to consider adding this feature in the future.

Hi DeShawn Morris, welcome to the Community! Thank you very much for supporting this idea and for your detailed comment! Our Product Team is aware of the popularity of this suggestion and we will be glad to share updates with you if we are informed of any changes 👍

Please, feel free to visit our New to Community forum to get the most out of your experience with our Community 🙂

This would be a huge development for my team as well. Not only having the description listed in the subitem, but having attachments included as well. From my point of view, it doesn't make sense to create a subtask without details from the subtask. Counterproductive, in my opinion, 

Thank you for adding your feedback Brandon Dunham 👍

I would also like to see subtasks created from dynamic forms inherit the name, description and attachments from the main task and specific follow-up questions for that subtask.