Scott Bassett
My feedback
7 results found
-
54 votes
An error occurred while saving the comment -
7 votes
An error occurred while saving the comment In addition there are certain default Jira things that are set, like all priorities for us are set as 'blocker' automatically when I create an issue in jira from uservoice, which is another thing I have to remember to change each time
-
26 votes
An error occurred while saving the comment This is probably the biggest pain point for us right now in keeping data in UserVoice updated. We have documented in our process for Product Managers to update things to 'in progress' when they are started and would love to be able to auto update things in UV based on some configuration that we define. This is an extra step that our product team often forgets to do with everything else going on.
I get the general stance that 'done' in jira doesn't necessarily mean 'done' for customers/uservoice, but the configuration should allow us to make those decisions.
The most important one for us is updating to 'in progress' in UserVoice when a Jira ticket has work started on it since this is largely driven by engineers who don't need to worry about UserVoice statuses. For us we have as part of our release process a person that updates items to 'relesed' in uservoice when we do ship/roll out the functionality, so the 'in progress' updates are the ones that have been most challenging for us to ensure we're updating.
-
9 votes
-
94 votes
-
15 votes
We're exploring this idea and need your help!
Instead of "No Status," as the default status, what would you like the initial status once an idea comes through to be labeled as?
An error occurred while saving the comment I'd also love this, the idea of no status meaning 'new' kinda is a work-around, but being able to configure what the initial status would be like you can features would be great
-
6 votes
An error occurred while saving the comment Sort by X then by Y, totally agreed!
This
We've created multiple faux user accounts with the ability to manage a email distribution list on the backend to enable all individuals to utilize a single account for their company.
While our CSMs and client facing roles have access to the admin to see all ideas associated to an 'Account', individual client contacts can't view details across their account if multiple individuals are submitting ideas.