Request Forms: Map Responses with Multi-Select

Thank you for another interesting suggestion Desiree Dixon, I'm passing it on to the team now 👍

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

I like this suggestion Desiree Dixon! More flexible request forms since request forms are great to use and could be even greater!

Hi Anders Kilbrandt, thank you for supporting this suggestion! Please make sure to +1 (= "like") Desiree's post if you haven't yet 👍

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

This would be very helpful for our team as well

Hey Greg Leff, thanks for letting us know. 

We've passed this on to the team 👍

Elaine Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Elaine Wrike Team member Become a Wrike expert with Wrike Discover

This would be useful for us

Thanks for supporting Jon Moakes, we'll make sure to update here if we have any news 👍🏼

Cansu Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Cansu Wrike Team member Become a Wrike expert with Wrike Discover

This would be an incredibly helpful, I've been meaning to make a product feedback thread for it for a while (in fact I thought I already had), so thank you for raising this Desiree Dixon.

Would really appreciate this one Wrike 😉😁

User cases for us:

-Retaining originally requested dates in custom fields (not in the stream) as well as mapping to the task S/E dates (which could then be modified by a project manager as appropriate).

-Wanting something to be mapped to the title and to a custom field. Saves me having to make the question twice, particularly annoying if it's a large dropdown with 50+ items. Saves the request form users from having to enter the same thing twice in two questions.

Cansu Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Cansu Wrike Team member Become a Wrike expert with Wrike Discover

Howdy Cansu,

Thank you and I have done!

Have a great day,

-George

George Fiveash Yes, absolutely - I do not want people to have to enter the same data twice, so that it can be mapped to two places. Not a great user experience 😅

Cansu Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Cansu Wrike Team member Become a Wrike expert with Wrike Discover

This would increase efficiency for us.  Here is are our current use cases:

• When transporting code from one environment to another, we require the developers to enter a request.  We need to approve these requests as well as be able to report on them from an audit perspective (which is why we need the custom fields).
• During our projects, if someone wants to make a change or enhancement to an approved design or already-built set of code, they need to enter a request.  We need to approve these requests as well as be able to report on which objects are impacted, hence the need for custom fields.

As a workaround, we are asking users to enter the information twice into 2 different fields - once so it can go into the description for ease of approving, and once so it can go into the custom field so we can report on it.

Hi Stephanie Bannister, thank you for sharing your use cases, I've passed them on to our Product team.

There is a post here, could you please check it out and let me know if this is similar to your use case?

If so, please upvote that post too. Here is a useful article explaining what happens after we receive Product feedback 🖊

Cansu Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Cansu Wrike Team member Become a Wrike expert with Wrike Discover

Hi Cansu,

That post is not quite the same - The forms as they exist today do allow custom fields to map at the task level, so the request here might already be resolved.

My use case is centered around allowing 1 input field (i.e. a short answer) to be mapped to both a task custom field and the task description.

Hi Stephanie Bannister, thanks for the clarification here, I've passed on your use case to our team 👍🏼

Cansu Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Cansu Wrike Team member Become a Wrike expert with Wrike Discover

Any news on this feature request please?

Hello Jon Moakes, thank you for checking in!

Unfortunately, no news at the moment. We'll be sure to update you here if there are any changes 🙋🏻‍♀️

Cansu Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Cansu Wrike Team member Become a Wrike expert with Wrike Discover

This would be helpful for us as well. Like the ability to have custom fields, but need more flexibility with how that information is viewed/used.