General Feedback
How should we improve our feedback and product management tools?
We are listening and use this feedback to prioritize our roadmap!
99 results found
-
Include relevant details from a location when a user reports a map issue! Include relevant details from a location when a user reports a map issue! -- Always someone asks us back what the street name was, the cross street info, and other information that we no longer have access to because it has been DAYS ago and we've moved on along down the road.
IF Waze included the details &/or allowed us to "see" what we reported - even a screenshot, we might be able to provide the information you ask. However, each time I am asked that - it is like - do we have photographic memory and /or esp? Because…
1 vote -
Rename Roadmap in admin console As an admin, I'd like an ability to rename Roadmap page in admin console. Currently we don't plan to share this Roadmap and tend to use it for only a limited amount of features. Our internal users get confused with word "Roadmap", since we use same word in our other applications. It would be great if I'll have ability to rename this page by myself in configuration. Another option is to simple rename this page to "Feature Board".
1 vote -
Make it possible to enter code in an idea description Even if it is not a majority use case for the kinds of products that UserVoice supports, there will be times when technical users want to add feedback that includes programming code.
It should be possible to receive and sanitise code just like StackExchange do…
<div> But it isn’t. <span>in a way that remains readable.</span> </div>1 vote -
Poor usability of ‘Describe your idea’ textarea The ‘Describe your idea’ textarea is set at a height of 5em with
resize:none. This is unhelpfully restrictive and makes entering anything more than 5 lines of text a complete pain.The simple solution is to remove
resize:noneor, if that is too great a stretch, useresize:verticalinstead.1 vote -
Accessibility/usability concerns: text styling This idea text manifests as light grey text (#87898F) on a white ground, which fails the minimum recommended contrast ratio.
Comments on ideas are rendered as 13px text on too long line lengths. The recommended base size for prose text is 16px or 1rem.
1 vote -
Accessibility concerns: form inputs UserVoice uses the following markup pattern for its user idea inputs:
<label> <span class="uvFieldPlaceholder">Label text</span> <input> </label>…which looks good at first glance until it becomes apparent that as soon as one starts typing in a field,
uvFieldPlaceholderis hidden with display:none and is therefore inaccessible.Additionally, when editing a previously posted idea, the form <label>s containing the inputs have no text at all.
1 vote -
improve roadmap portal for end users by coloring the cards by feature type improve rooadmap UI for front-end user: let us set card colors so we can more easily identify what type of feature it is (we need to be able to set a field type with a color that is then applied on the card) on the roadmap settings)
See good examples from competitors here https://www.aha.io/product/integrations/rally (there are plenty of other little UI aspects you could learn)1 vote -
as a front-end users, Subscribe to roadmap updates for digests (rather than individual "follow" on each roadmap item) improve the usability of roadmap for end users:
the roadmap page for full editor roles has a "subscription" button to get notifications for items that are changing in a digest. This button should be made available to any of our users who have access to the published roadmap. It's good to have "follow" on individual items but it's much better to have a digest of all changes if the users want to.1 vote -
Scale the Roadmap feature with products area/products grouping for the roadmap feature, you use product area but it's way too simplistic.
We need product area (ie business capability) groupings, and then "products" (to which we attach a feature). Using a custom field for "Tags" for Products isn't good as it's not consistent taxonomy so impossible to manage. Also, using Custom Fields Select type isn't possible either as you only have 50 entries for Select type fields - not enough. Please help us address that asap!!1 vote -
More granular internal roadmap feature search capabilities We have hundreds of features in our roadmap and the Contributor portal roadmap view does not provide the capability for the user to search for a keyword of a Feature and show where it is on the roadmap. It is very difficult to find where a feature is. There are categories but this is not fine enough.
1 vote -
Ability to reorder Roadmap columns in table view Add the ability to drag and drop roadmap columns in the order of the user's preference.
1 vote -
Responsive Roadmap Statuses As a user, I want the status columns to be responsive, which typically means I want it to be the full width of the page at all times, responsively changing to fit the width of the page.
1 vote -
An option to set permissions for anyone with roadmap URL The page you’re directed to when browsing the URL to your internal roadmap is a read only page. Only admins from inside the admin console of the UserVoice UI have permission to alter the cards or buckets on the roadmap. We would like an ability to allow users to take actions on this page.
1 vote -
Real-time updates when viewing the Roadmap In cases where a copy of the roadmap is being shared internally and viewable on a display within a common area (for example), it would be nice if the board updated automatically when cards are added, removed, or moved. This would prevent having to refresh the page in order to see recent changes.
1 vote -
1 vote
-
1 vote
-
Do not require hh;mm:ss in date field in UI for editing features Seems a bit much to have to fill in the hh:mm:ss fields.
1 voteHi Everyone,
We have reviewed this idea, and it’s not something we plan to implement. Even though we are deferring this idea for now, it is still open to votes and comments. We do want to hear your opinion. Thank you for the feedback, and please, keep sharing!
-
Score Feature based on Number of Comments and Notes For feature scoring, it would be helpful to also be able to score based on the number of comments and number of notes as this also is a measure of pervasiveness and urgency of the problem
1 voteHi Everyone,
We have reviewed this idea, and it’s not something we plan to implement. Even though we are deferring this idea for now, it is still open to votes and comments. We do want to hear your opinion. Thank you for the feedback, and please, keep sharing!
-
Report of Followers of Features on Internal Roadmap Have a report or list of followers for who follows features on the internal roadmap
0 votes
- Don't see your idea?