I like this idea. It would help us prioritize to know more about the environment of the person suggesting the idea.

This is very important for our project. The basics like idea title and description are not enough and to be able to take content into such custom fields, for now we have to create an additional step in our internal workflow. If we can create custom fields while taking initial idea, this additional step and iteration is reduced.

Even having a drop down that could toggle questions based on your initial response. For example say the first drop-down is a subcategory choice that contains of 2 options. The other drop-downs or required fields that would populate would be dependent of that choice.

This would be super helpful if we could create a custom field, with parameters we define and make this a requirement. Currently this functionality is missing and we are having to create a bandaid solution till this feature has been implemented.

This is a very important and ideal feature when submitting and receiving detailed feedback to take action on. Also allows for better feedback structuring when analysis or research is done. Supports quicker turn around time, since detailed info is provided the first time instead of requiring back & fourth discussion.

Custom fields are a requirement in order for us to better exploit Uservoice internally and increase our effectiveness in providing service. This is critical for our internal feedback system. The existence of custom fields would allow us to capture pertinent information by having our team fill out and capture necessary details that are required for simplification of communication channels and in achieving success. The ability to create drop down menus with pre-polulated responses would be a massive improvement to our workflow and ability to have consistent messaging.

This would be very useful for us to create some very easy integrations between UserVoice and our own internal tools for product backlog management.

Without this we are forced to a do a single import and then make sure that every new idea that is added we immediately address through our internal tooling or we fall out of sync with UserVoice and then have no way of knowing which ideas are missing from our internal tools and with over 1,000 ideas, that is going to be very tricky to manage.

The ability to do this is crucial for our internal feedback system. The additional fields would allow our support team members to fill out pertinent information that we have the ability to define. Even allowing for a drop down field of yes/no and 1-10.

This would be an essential aspect of the feedback process for our organisation. Also having the ability to add tags to help categorise, filter and search ideas.

This will be immensely helpful.

I am going to piggy back on some of the comments made here. I would like to see a way to send fields on the query string that can be collected in the backend which give more context on the idea itself - such as identifying what part of the portal my customer was on - when he clicked Give Feedback. These fields would be inferred by my system and would add correlation id's or other tags that I can log in my system to give me more information on user context when looking at my system logs so that I can better help decipher the user's feedback.

An additon to my previous comment: in the described example, this info would of course only be visible for admins and not to the users.

We would benefit from having simple checkbox fields that can be used as filters / sort criteria when listing ideas. For instance, has the idea been reviewed by product management yes/no, Do we think the idea is innovative (or matching any other prioritized criteria of choice) yes/no. Etc. This kind of functionality would make our processing of ideas easlier within uservoice itself.

The administrator also needs to be able to define whether the custom field is visible to customers or not. There lots of internal uses where only administrators can manage and read the field.

We would like a custom field that reflect whether an idea has been created within our change management system (JIRA). So just a URL field would be great.
This field then needs to be included when we export all ideas into excel

We would like this as well. Our main problem with ideas today is that we tend to get too little context and detail about each idea. With custom fields we feel we would be able to steer the end user to give enough detail, while at the same time making all ideas in a similair format.

(For our main ideas forum we only have company-internal end users):
The base of our use case would be to force the end user to input scenario as well as context and other important aspects. We would also to classify each idea as for example [low/medum/high] business impact, to sort into several categories and to input any due time constraints.

Seconding Meredith's use case--we want to be able to have fields (internal and public-facing) that will help us organize ideas within uservoice. we were going to upgrade to get all of the ticketing customization options (like being able to queue to a specific product team), but since none of those are available for ideas and we already have separate ticketing systems (for tech and support), we don't see the benefit.

Even if you didn't go down the road of new fields with data types and such, a tag/label concept for ideas (like gmail's approach) would help people accomplish many use cases.

I would use this to document the delivery date of the idea and/or the release it's associated with.

Along with this, I'd really like to be able to permalink to all ideas with that value. http://ideas.example.com/something-that-finds-the-ideas-with-a-specific-value

In addition to the UI experience details already provided, a hidden custom field for internal categorization would help with our need for an integration with our software project management tool.