Linking Customer Feedback to Jira and DevOps
Link ideas to Jira issues and Azure DevOps work items, so engineers see customer demand and product sees delivery status.
On this page
Link UserVoice ideas to the Jira issues and Azure DevOps work items that deliver them. Engineers see the demand behind the work, and product sees each issue's status. This guide covers setup, linking, what syncs, what engineers see, and routines that keep both sides current.
What the connection does
The connection links UserVoice ideas and features to Jira issues or Azure DevOps work items, and shows each side's status on the other.
A linked issue shows the ideas behind it, with their status and number of supporters.
Each linked issue or work item shows its current status on the idea in UserVoice.
Link an issue that already exists, or create a new one from the idea.
One idea can link to several issues, and one issue can carry many ideas.
| Jira | Azure DevOps | |
|---|---|---|
| Editions | Jira Cloud and Jira Data Center | Azure DevOps organizations |
| Link from | Ideas and features in UserVoice, and the issue in Jira | Ideas and features in UserVoice |
| Shows in the tracker | A UserVoice panel and fields on each linked issue | A UserVoice tag, a comment, and a link on each work item |
The integrations depend on your plan. Your UserVoice rep can confirm whether Jira or Azure DevOps is included.
Connect Jira
Connecting takes a UserVoice admin who can change settings and a Jira admin. Pick your Jira edition, then follow its steps.
Jira Cloud
- A Jira admin installs UserVoice for Jira from the Atlassian Marketplace.
- In UserVoice, go to Settings, open Integrations, and choose Jira. Select Link account…, choose Jira Cloud, and enter your Jira site URL.
- In Jira, the Jira admin opens Settings → Marketplace apps → UserVoice, checks the request is from your company's UserVoice account, and selects Approve.
- UserVoice shows the site as Connected. Jira finishes adding the UserVoice fields, normally within an hour.
Choose what UserVoice shows in Jira. On the same Jira page, a Jira admin decides whether to Show customer revenue (MRR) on issues, and whether to Let people who can edit an issue link and unlink ideas from Jira.
Jira Data Center
- In UserVoice, go to Settings, open Integrations, and choose Jira. Select Link account…, choose Jira Data Center, and enter your Jira URL.
- Open Jira Admin Server Installation Instructions. If you aren't a Jira admin, send the page to one.
- The Jira admin creates an application link in Jira, under Settings → Applications → Application Links, using the values the page gives.
- The Jira admin selects Generate Authorization URL, authorizes UserVoice, and can select Check Status to confirm.
- In Jira, the admin sets the UserVoice Links field to the Wiki Style renderer, and adds it to the screens of each project where you want to create issues from UserVoice.
UserVoice has to reach your Jira. If Jira Data Center sits behind a firewall, it must allow traffic from UserVoice, or authorization fails. The UserVoice help site covers the firewall setup.
Data Center issues show UserVoice in one field. The UserVoice Links field lists each linked idea and feature. Jira Cloud issues get the UserVoice panel and fields covered in What engineers see.
Connect Azure DevOps
Azure DevOps connects with a sign-in. The person who signs in must be an Azure DevOps administrator.
- In UserVoice, go to Settings, open Integrations, and choose Azure DevOps.
- Select Link account… and sign in. If you aren't an Azure DevOps admin, send the link to one.
- Choose the Azure DevOps organization to use, and select Confirm Azure DevOps account. UserVoice loads its projects; you can leave the page while it does.
- Choose Automatically enable all projects and work item types, or Manually select which work item types can be created from ideas.
- Select Save changes.
| Choose | When |
|---|---|
| Automatically enable all projects and work item types | Every team should be able to create any work item from an idea |
| Manually select work item types | You want ideas to become only certain types, such as User Story or Feature, in certain projects |
Start narrow. Enabling only the projects and types product teams plan in keeps the create form short and stops ideas landing in the wrong backlog.
Link or create an issue
Open the idea and find Integrations in the panel on the right. It lists linked Jira issues and Azure DevOps work items, with their status.
| To | In Jira | In Azure DevOps |
|---|---|---|
| Link existing work | Select Add issue, then Link Jira Issue, and paste the issue URL or key, such as ABC-1234 | Select Add work item, then Link to an existing item |
| Create new work | Select Add issue, then Create new Jira Issue. Jira's create form opens with the idea's title and description filled in. The new issue is linked when you create it. | Select Add work item, then Create a new item, and choose the project and work item type |
| Remove a link | Unlink the issue from the idea. You can link it again later. | Unlink the work item from the idea. UserVoice adds a comment to the work item saying who unlinked it. |
- Features link the same way. Link a feature when a single piece of work answers several ideas.
- Linking needs edit access to feedback. View-only admins see linked issues but can't add or remove them.
- On Jira Cloud, people who can edit an issue can also link and unlink ideas from the UserVoice panel in Jira, if a Jira admin allows it.
What syncs, and which way
Each side shows the other's details. Neither tool changes the other's status.
| What | Direction | Details |
|---|---|---|
| Issue status | Tracker → UserVoice | The idea shows each linked issue's or work item's current status |
| Issue details | Jira → UserVoice | Key, summary, and type. On Jira Cloud, also assignee, release, sprint, and progress. |
| Idea details | UserVoice → Jira | Each linked idea's and feature's title, status, and supporters, kept current as they change |
| Accounts and revenue | UserVoice → Jira Cloud | Accounts and monthly revenue behind the linked ideas, if a Jira admin turns revenue on |
| The link itself | UserVoice → Azure DevOps | A UserVoice tag, a comment with the idea's title and text, and a link to the idea |
| Deleted issues | Tracker → UserVoice | Deleting the issue or work item removes its link from the idea |
Idea statuses don't change on their own. When a linked issue moves to Done, the idea's status in UserVoice stays as it was. Update the idea, with a message, so its supporters hear the news.
Let your AI assistant close the gap. Connect the UserVoice MCP and the Jira or Azure DevOps MCP server to the same assistant. Ask it to find issues that moved to Done, follow each one's UserVoice link to its ideas, and draft the Completed updates. It sets the statuses, up to 25 ideas at a time, once you confirm.
What engineers see
Engineers see customer demand in the tracker they already use. Opening an idea from the tracker takes them to UserVoice.
| Where | What they see |
|---|---|
| Jira Cloud: the UserVoice panel | Linked ideas and features with status and supporters, totals for ideas, supporters, accounts, and revenue, and the top accounts asking |
| Jira Cloud: UserVoice fields | UserVoice, UserVoice Ideas, UserVoice Supporters, and UserVoice Revenue, for board cards, list views, and JQL |
| Jira Data Center: UserVoice Links | Each linked idea and feature, with its status and number of users |
| Azure DevOps work item | A UserVoice tag, a comment naming who linked it with the idea's title and text, and a link to the idea |
Sort the backlog by demand. On Jira Cloud, add UserVoice Supporters to your list view, or search the UserVoice fields with JQL, to see which issues carry the most customer weight.
The UserVoice fields in Jira are read-only. UserVoice writes them. Edits made in Jira are overwritten the next time an idea changes.
Routines that work
The link is worth most when it's made early and checked when work ships.
| When | Do this |
|---|---|
| During triage | Link new ideas to issues that already exist, so the issue's demand stays current. |
| At planning | Create or link an issue for every idea or feature going into a sprint or release. Engineers then start with the customer context. |
| Each week | Check ideas whose linked issues moved to Done. Update their status with a short message. |
| When work ships | Update every linked idea, including merged ones, and point to your release notes. |
Link every issue that delivers part of an idea, such as an API change and a UI change. The idea shows each one's status.
Link related ideas to the same epic, or link them to a feature and link the feature to the epic. The epic's UserVoice details then cover them all.
Link from your AI assistant
With the UserVoice MCP connected, your AI assistant can link an idea to an existing Jira issue or Azure DevOps work item. The UserVoice agent can do the same in the admin console.
- Name the idea and the issue: a Jira key such as ABC-123, an Azure DevOps work item ID, or the issue's URL.
- The assistant checks the issue and shows you what will change.
- Confirm, and the link is made. Nothing changes until you do.
- Links only. The assistant links ideas to issues that already exist. It doesn't create, edit, or unlink issues.
- Same tracker only. It links issues from the Jira site or Azure DevOps organization connected to UserVoice, and refuses others.
- The tracker updates too. In Jira, the issue's UserVoice details update. In Azure DevOps, the work item gets the UserVoice tag, a comment naming you, and a link to the idea.
Create in Jira, link in UserVoice. Connect your Jira MCP alongside UserVoice. Ask your assistant to draft and create the issue with the idea's customer context, then link the new issue back to the idea.
Troubleshooting and good habits
Most problems come from approval, permissions, or a link that was never made.
| If | Try this |
|---|---|
| Jira Cloud shows “Waiting for approval” | Ask a Jira admin to approve the request in Settings → Marketplace apps → UserVoice. |
| Jira Cloud shows “Uninstalled” | A Jira admin reinstalls UserVoice for Jira from the Atlassian Marketplace. |
| Data Center authorization fails | Check the application link values, and that your firewall lets UserVoice reach Jira. |
| Data Center can't create issues in a project | Add the UserVoice Links field to that project's create screen. |
| Linked issue details look out of date | Select Force Issue Resync on the Jira settings page. |
| No Add issue or Add work item button | You need edit access to feedback. Ask a UserVoice admin. |
| A link disappeared | The issue or work item was deleted in the tracker. |
Deleting the Jira configuration removes every link. All issue links on your ideas and features are removed and can't be recovered.
Good habits
- Link the work that delivers the idea, not every issue that mentions it. Engineers trust the counts when links are deliberate.
- Merge duplicates before you link. When you merge ideas, their links move to the idea you keep, so totals in the tracker stay right.
- Link features for big pieces of work. One feature linked to an epic is easier to keep current than twenty ideas each linked by hand.
- Give engineers view-only access. They can open an idea from the tracker and read every customer's feedback, without changing anything.
- Make closing the loop someone's job. Name who updates linked ideas when an issue moves to Done, and when.
If it's in a sprint, it's linked. A practical starting point: every idea or feature committed to a sprint or release has at least one linked issue before work starts.
Try it with your AI assistant
1 of 4 prompts in the PDFAttach the PDF to Claude, ChatGPT, or another assistant, then paste:
Using the UserVoice guide I attached, help me plan connecting [Jira Cloud, Jira Data Center, or Azure DevOps]. Ask me about our projects, who our tracker admins are, and how our teams plan first.
Three more prompts and the checklist are in the full guide. Get it by email →
Read next
Get the full guide
We'll email you the 14-page PDF. It adds two things that aren't on this page:
- A six-step checklist to put the guide into practice
- Four AI prompts for Claude, ChatGPT, or your assistant of choice, including one that uses the UserVoice MCP to work with your own feedback data
