Do not include unanswered questions from a request form in description of project

We ask that our staff use Wrike request forms to "order" items from our department. All items that are available are listed individually as questions and staff simply indicate the quantity they need of each. After submission, each response is mapped to the Description field of the project that is created for each request. However, ALL the items/questions are left in the description field even if staff didn't request that item. We would find it helpful if Wrike can prevent unanswered questions from being displayed in the description field of the project. We only want to see items that are requested. Items not requested are irrelevant to the project and therefore just cause more clutter.
Would anyone else find this helpful?

Upvote 16
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
10 commentaires

This would be useful for us, as long as it was optional by request form. We have a number where the info is not mandatory but often collected at a later date. Having the questions there enables the PM to remember which info needs collecting

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hi Lorie Saria-Huertas! Have you considered just using an open field so that in each request it could be populated by items needed in every particular case?

 Anyway, this is very interesting feedback, and it's passed on to the team, thank you! 

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

1
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hi Lisa,

I suppose that's an option. But it's a request form that includes all the options of our stock and supplies, which are a lot of items. Creating an open field would rely on staff remembering what's available, which violates the heuristic principle "recognition rather than recall". Listing every item as a question allows us to require them to be specific with the type of item they need, which can prevent any follow-up, back and forth questions. 

1
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
Avatar
Hugh

Hi Lorie Saria-Huertas, thank you for the use case. It's been passed on to our Product team.

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Lorie,

I asked the same question and was directed here to your thread.  I wanted to build a form to request changes to our CMR system, but the current form has about 20 fields on it and you may only need to fill out 2 or 3 in the request.  On my trial run of it, I noticed that all of the empty fields just show up as a list, and its hard to discern the important information.

Here's hoping this can be implemented! 🤞

1
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hi Lori & Wrike team. I've also requested this. We use request forms for all projects and some questions are mandatory that require the brief owner to fill out and some answers are not needed for all projects. Reason why the question aren't mandatory in the form. It would be amazing if a question isn't mandatory and isn't filled out that they would disappear once the form was submitted. 

1
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
Avatar
Cansu

Hi Angela Raykovich, welcome to the Community!

Thank you for sharing your feedback here, I've passed it on to our Product team. Here's an article that explains what happens with Product Feedback that we receive here on the Community. If you'd like to learn more about our Community, please check out our New to Community forum 🙋🏻‍♀️

Cansu Community Team at Wrike Wrike Product Manager En savoir plus sur les fonctionalités et les meilleures pratiques grace à nos Webinaires online

Cansu Wrike Team member En savoir plus sur les fonctionalités et les meilleures pratiques grace à nos Webinaires online

1
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

I submitted a post yesterday as well for this same thing but for a different reason. Yes, sometimes unanswered questions help remind us we need them, but if there "not required" we don't need them. So having the ability for them not to show up in the submitted brief would be a huge help and remove the "clutter" as indicated above. 

2
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hi Aimee Reistad, thanks so much for adding your interest and feedback on this with us here. We've passed this on to the team 👍

Elaine Community Team at Wrike Wrike Product Manager En savoir plus sur les fonctionalités et les meilleures pratiques grace à nos Webinaires online

Elaine Wrike Team member En savoir plus sur les fonctionalités et les meilleures pratiques grace à nos Webinaires online

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hi  Lorie Saria-Huertas,

I support your request in general, but I think you could solve it in your case by using a custom (number) field for every item. It may be a lot of work to set it up, but after that you could calculate the numers automatically, so you could take advantage of it.

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Folllowing List for Post: Do not include unanswered questions from a request form in description of project
[this list is visible for admins and agents only]

Haut de la page
Didn’t find what you were looking for? Write new post