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.
Claire Talbott
shared this idea
Hey there! 👋
This week we released Custom Fields on ideas for internal use. This solves a problem for much of the feedback we received on this idea, but not all of it. We will keep this idea open for additional feedback and votes, but for those who were requesting better ways to organize ideas internally, we hope you enjoy our new release! You can read more about it here.
-
Watchman
commented
Would this be the same idea as using the custom fields in the knowledgebase?
We have our client's subscription passed via SSO to uservoice, and I'd love to use it to build URL's in articles that are custom to a user's account.
-
John Wolf
commented
Our needs are similar to Meredith's. I would like to add fields to note which product manager has been assigned the idea, when we will release it, and the stage within the requirements process. These would all be private fields.
-
Jacob J
commented
I`d like something similar to Meredith`s comment. I want to be able to associate a project to each idea. That way, when we are ready to pull requirements for a project, we can easily use an admin only field that users cannot see.
-
Matthew Tschiegg
commented
Just checking out out UserVoice for the first time and this feature would be nice to have to track user specific info behind the scenes, info such as browser, href, OS, etc.
-
Pixel Pandemic Support
commented
In our case we just need read-only (hidden) fields to be passed along on ideas (as they are on tickets now).
-
Steve Pachter
commented
This would be important for us, even if it's just collected via custom data submitted in javascript like for problem tickets.
-
Dan
commented
We would like to see new fields for both admin and customer-facing metadata.
-
Meredith Zachritz
commented
We are trying to use uservoice for more than just collection of ideas. We'd like to manage review and prioritization of those ideas for inclusion in backlogs for new releases. We can't do any sort of rating or more sophisticated classification without something like a custom fields feature. Ideally, we could also decide what fields would be visible to the public in our public forums (e.g., some fields would be for internal use and viewing only).
-
juhasev
commented
The most important thing here would be to able to pass script location or some identifying information where the user was in the application when he/she gave feedback. This way you can associate feedback with a particular feature/page. Imagine getting feedback that says "The submit button is too small".
-
ryanparedez
commented
this is a good idea, but it might also be helpful to allow the customer to add a time stamp. They may not know what it takes to add new features to a particular site, but by the time you maybe implement that new idea, they could of moved on(hopefully not). Even if the data is meaningless, it would still be cool to know if you can compromise with the timeframe they would expect.
-
Jason Carley
commented
When collecting ideas we need to have more than just the title and description. Other fields, such as associated budget, problem analysis, etc. would be useful. The administrator would also need to define the field type, if its required, and validation patterns.
-
Richard White commented
@binaryfeed I agree with you and I don't subscribe the "all bugs must be squashed" before all else mentality. If I did I wouldn't ever get out from fixing legacy browser bugs :)
We're making this official stand because that's not how *most* people approach it. Most people want a classic bug tracking system that's not what we do. Feel free to continue to direct your users to put bugs in UV.
-
binaryfeed
commented
Wow. This is a bad decision. Knowing how important fixing a bug is based on how many users have voted for it is one of the key value propositions of UserVoice. Doing the hand-wave of "all bugs should be fixed anyway" ignores the fact that some bugs simply don't bother users, while others are real killers. Bummer.
-
Votes are actually returned when an idea is declined.
-
Malk'Zameth
commented
Cheers! ;D, but:
clearly, and I thought it was already the case, people should get their votes back when one Idea is declined, Is kinda of a bug really. -
@malk.zameth You took the words right out of my mouth :)
-
Malk'Zameth
commented
this tools its a brillliant idea og general user feedback, but turning it into a full fledged bug control system (like trac, bugzilla, flyspray etc) would make it lose focus, it is better to leave bug tracking to other apps and focus on general user feedback (which WILL include a bug from time to time)
-
metavida
commented
If you allow tagging or admin-created categories (http://uservoice.uservoice.com/suggestions/2322) wouldn't that basically also cover this need? I mean other than tmetro's nifty suggestion about rewarding bug reports. If so vote for 2322 :-)
-
metavida
commented
If you allow tagging or admin-created categories (http://uservoice.uservoice.com/suggestions/2322) wouldn't that basically also cover this need? I mean other than tmetro's nifty suggestion about rewarding bug reports. If so vote for 2322 :-)
-
[Deleted User]
commented
We decided to use UserVoice only for feature requests and not for bug reports for now. We feel that bugs should be fixed anyway, not depending on how many people are voting for it..