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?

8
5 comments
Spot On Innovative Approach Stellar Advice
Avatar

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
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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 Become a Wrike expert with Wrike Discover

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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. 

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar
Hugh

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

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

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! 🤞

0
Comment actions Permalink

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]

Didn’t find what you were looking for? Write new post