General Feedback
How should we improve our feedback and product management tools?
We are listening and use this feedback to prioritize our roadmap!
106 results found
-
More Flexibility in Roadmap Visibility / Sharing with Contributors When try to use the Roadmap feature or other things to reflect our decisions externally, if we want to give people only the view only access its too limited information they can only see the title and they cannot see the discussion and Jira integration to reflect the epic status. If we give collaboration access, then its too much access.
2 votes -
Attachments and Comments in Roadmap Ability to add attachments and have internal comments on each feature in the Discovery roadmap
3 votes -
Ability to view feature audit As an admin I want to have an ability to see log of feature changes. Currently, if I change fields in Idea, I see history of changes. I need similar behavior for feature.
1 vote -
Add Select All to Features Add select all when adding ideas to a feature
1 vote -
Add referral link for Linked Ideas without Feedback attached For linked ideas that have no feedback yet, there is no button to click to return to the original idea within the roadmap feature.
1 vote -
1 vote
-
1 vote
-
Change requirements of fields when creating a roadmap feature Owners can determine what field is required to be filled when admins are creating a roadmap feature.
1 vote -
Ability to add ownership to a feature in the internal roadmap I would like to have each team create the feature they want to work on in the internal roadmap. In using it in this way, it would be great to pull in our internal labels. Or the ability to identify the owner or team owning the specific feature.
2 votes -
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 -
Roadmap permissions I would like to be able to have restricted permission on the Roadmap so we can enable people to see it in the app but not have any edit permissions. Similar to what you can do with ideas.
5 votes -
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 -
Add a ‘User interface’ or ‘General feedback’ Category as the categories provided are too restrictive I am posting this and other recent feedback ideas in ‘Roadmap’ not because they belong there, but because there is nowhere appropriate to put them!
2 votes -
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 -
Share roadmap with a specific contributor team Provide the ability for Admins to specify which contributor group has access to view the roadmap from the contributor console instead of providing all contributors access.
4 votes -
6 votes
Hi 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!
-
Archive or Hide Roadmap Features We would like the ability to archive or hide roadmap features, specifically once those features have been completed and released. I know the "No Status" will not show up in the swimlanes but it would be great to either hide or have the ability to archive features that end up in our "Fully Launched" status (otherwise we'll eventually end up with a huge column of features)
5 votes -
Product Board Connection As I mentioned, we currently use Productboard for our roadmapping component. When we bought UV, we had hoped that the UV zap would be able to connect both tools so that we could get the best of both worlds.
Since the UV zap is depreciated, we haven't been able to connect those two systems. This often means that we might be working on features but it's not reflected in UV.
It's created a few challenges. Most notably, it makes it hard for customer-facing team to stay up to date with what's happening with their ideas.
I've been trying to think…
2 votes
- Don't see your idea?