Jira is the Development team view of their work. UserVoice is the customers view.

The current integration show the Jira status, but does not change the status of the Idea. The idea is for the Jira status change to automatically or prompt the Jira (user) to change the associated Idea status.

It's probably more complicated than a simple 1 to 1 linking. Needs more investigation. I seen where a Idea gets linked to a parent of a collection of Jira issues and one or more of them need to be completed to close the Idea. So the manual progress or prompt for the Jira user to update Uservoice is probably better choice until we implment a higher fidelity process.

I would like Jira statuses to automatically update and reflect in the Roadmap Statuses to help reduce work

I would want to define a template for updates that would come from a status change. For example, when one connected Jira goes into our status of "In Design" have a templated response in UserVoice that would say something like "[Great news! We've begun designing the solution for [idea name]. Expect to see it in a future release."

If there are many connected Jiras for an idea, then when one Jira is "Released to Production", then have an automated templated update for each jira updates until the final connected jira is released. For each iteration, something that would allow us to say "A new capability has been added to [Forum] to solve [idea name] check out our release notes [link] to learn more!] For the final update, allow a configured message for the formal completion of that idea.

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.

As a product manager I am constantly going back and forth trying to manage these different statuses for various stakeholders (i.e. Development, Customers, Support, Consulting). Having a way to map statuses and auto-update would be a huge time-saver