Add custom questions for users to fill out when creating an idea
When a user goes to create an idea, they only have to give a title. Often Product Teams want to ask their users for additional details and be able to make these fields required.
This allows Product Managers to get the full details they need from users when they post an idea, and limits them needing to follow up for more information.
Hi – we have spent time investigating this and talking with many of you, and have decided to defer from building this for the time being. In our conversations with customers, we came across many different use-cases for custom fields and think we could potentially provide better, native support for some of the common use-cases like “priority” or “impact” rather than attempting to solve several problems with this one feature. We may revisit this idea after providing out-of-box support for the most common use cases.
Kevin Praeger commented
I think that is the right choice to defer this project. This may be a nice feature in the future, but I would prefer to see more small enhancements and smaller additions and polishing to existing features.
We use UserVoice to gather Bug Reports & Feature Requests from users. The Vote mechanism is great because it helps us quantify the number of users that are affected by a bug or would like to see a feature implemented, but it does not help us quantify other very important metrics that would help us prioritize issues better. For instance, a minor issue that hundreds of users are experiencing is prioritized higher than a severe issue that only a few users are reporting. Because items with a high number of votes always have the limelight, issues with far greater consequences are always tucked away at the bottom of the list, encouraging our Product Managers to ignore issues that can devastate our reputation.
An example of 2 important metrics we need for bug reports include:
#1 Severity/Level of Impact
#2 Frequency of Occurrence.
For instance, you could have a bug that is severe and has a high level of impact, but it only occurs once per year. On the other end of the spectrum, you have a minor irritation that occurs hundreds of times per day. A minor irritation that occurs hundreds of times per day in many cases should be prioritized higher than a severe issue that occurs once per year. As you can see, number of votes does not answer these critical questions.
We would like to be able to ask the following questions, and have multiple choice answers that have a numeric value to them to help us sort and prioritize things. For instance:
Question #1 What level of impact does this bug have on your organization?
Answer #1 Minimal: A minor irritation, but I can work around it. Value: 4
Answer #2 Normal: Causes issues, but I can work around it. Value: 3
Answer #3 High: Causing significant disruptions, but I can work around it. Value: 2
Answer #4 Critical: Crippling my organization, causing data corruption, no workarounds available. Value: 1
Question #2 How often do you encounter this bug?
Answer #1 Rarely (< 1-2 times per month) Value: 5
Answer #2 Intermittentely (A few times per week) Value: 4
Answer #3 Regularly (Several times per week) Value: 3
Answer #4 Frequently (Several times per day) Value: 2
Answer #5 Constantly (More than 15 times per day) Value: 1
For Feature Requests, we would like to ask additional questions like:
#1 How much more productive would you be if we added this feature?
#2 Would adding this feature positively impact your revenue? (yes/no response)
#3 Would adding this feature help you make better clinical decisions? (we are a clinical system)
#4 Would adding this feature revolutionize your business?
We need to be able to customize the questions and responses so that we can frame the questions and answer to get the most value out of them, then we need to be able to create views that sort the responses reliably so that we can make better decisions on what to work on next. It would also be nice to have questions that have freetext answers.
Ideally, when another user votes for an existing issue, they should be given the opportunity to answer those questions as well. If this requirement complicates things, we would much rather have just the contributor feedback than nothing, but adding the feedback from other voters would make the data even more valuable as we can see if other user responses corroborate with the contributor responses. Finally, the answers to the questions should have the option of remaining private/confidential as to not influence the answers of other voters, and allow us to ask probing questions that voters may not want to make public.
Not having basic features like custom fields to ask users important questions to help us determine the value/impact of an idea/bug like level/severity of impact and frequency of occurrence has significantly reduced the value of the data we are receiving from UserVoice, and has caused us on several occasions to look for a competing product. Number of users behind an idea is not the only metric that matters. As soon as a competitor offers a comparable Devops integration and search while the user is entering an idea we are leaving uservoice. Seeing that it takes nearly a decade for Uservoice to act on something as important as this despite using Uservoice in-house doesn't help. Adding this feature might influence us to stay.
Given the volume of interest, and extended timeline before a decision (7 years), which was more of a delay than a resolution, could we please get some feedback regarding expectations for these three features?
Are we starting from scratch?
What still remains before your team reviews this for development feasibility?
There were 300+ users supporting this, and now across all 3 we have about 20 each. These 3 topics have lost their momentum due to this split.
Yup, this is the part of the "allow custom fields for ideas" piece I want. I would love to know how many licenses they have or their tenant name