Aaron Hixson
My feedback
11 results found
-
6 votes
-
9 votes
Hey all,
Thanks for the feedback and support of this idea.
Upon rollout of the Contributor Console, this feedback helped us identify that we did not make it clear enough that the feedback captured from the Contributor Console is private.
That is, like with the contributor console, feedback associated to ideas on behalf of customers from the Contributor Console is always private.
We are working on a few updates to help make this more clear moving forward.
Thanks again.
An error occurred while saving the comment Aaron Hixson supported this idea · -
12 votesAaron Hixson shared this idea ·
-
20 votes
-
54 votes
An error occurred while saving the comment Aaron Hixson commentedOur most important enhancement request is so that customers can see all of the ideas from their organization - not just theirs. This would save us lots of manual time of having to run reports for our customers and allow them to be more self-service.
Aaron Hixson supported this idea · -
3 votes
Thank you for posting and sharing your feedback on this.
You are right. Silently archiving suggestion is not a good customer experience.
While we will need to decline ideas that don’t align with our Product Team’s vision, we need to communicate that to our customers.
We are declining this idea because we will have to close out suggestions, but we are going to work to communicate much more openly around this going forward.
If you have any questions around any feedback you have submitted, please reach out to me directly at claire.talbott@uservoice.com. I will be happy to look into this for you.
An error occurred while saving the comment Aaron Hixson commentedPersonally I'm fine with something being closed/archived if it was either delivered or there was a public status update stating why UserVoice PM has decided not to implement it.
Silently archiving though is not great.
Aaron Hixson supported this idea · -
4 votes
An error occurred while saving the comment Aaron Hixson commentedI agree - sometimes after doing a status update and getting customer feedback, we edit the original posting of the idea making the status update unecessary, redundant. It would be good to be able to completely delete/remove a status update if necessary.
Another example is onetime I accidentally chose the wrong status because I fat fingered it. I had to do another status update to choose the correct status, but I could remove/hide the accidental status update.
Aaron Hixson supported this idea · -
14 votesAaron Hixson supported this idea ·
-
26 votesAaron Hixson supported this idea ·
-
14 votes
An error occurred while saving the comment Aaron Hixson commentedAs a work-around, this could be done through your SAML Provider - where that tool implements the two factor auth for specified accounts and doesn't authentication and provide the SAML token to UserVoice until they pass both factors of authentication.
-
84 votesAaron Hixson supported this idea ·
I would love the role the contributor console out to our field - but as I was updating our documentation for how the field would use it, I noticed several critical features missing that make it a blocker for us. This is one of them