What can we help you with?

e.g. Gantt chart, Creating tasks, Sharing folders

Blog

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

5 comments

  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Dawn Kirby

    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

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Lisa

    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 ๐ŸŒŽDiscover... Wrike Discover and become a Wrike expert. Click here to get started

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Lorie Saria-Huertas

    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. 

    Is this helpful? 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.

    Hugh Community Team at Wrike ๐ŸŒŽDiscover... Wrike Discover and become a Wrike expert. Click here to get started

    Is this helpful? 0
    Comment actions Permalink
  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Mark Bernardo

    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! ๐Ÿคž

    Is this helpful? 0
    Comment actions Permalink

Please sign in to leave a comment.

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]

Community

Welcome ๐Ÿ––

Hi there! ๐Ÿ™‚ Want to become a black belt Wrike Ninja? Here's how to earn a Wrike badge

Welcome ๐Ÿ–– Have you checked out this week's Release Notes yet?

Hey! ๐Ÿ‘‹ Curious about something? Visit How To to search and ask the Community for answers.

Welcome! ๐Ÿ‘‹ Figured out a good tip or trick? Share it in Best Practices.

Want to connect your existing software to Wrike? Learn and ask how in the API section.