Released Hub vs 
UserVoice Released Hub is the best choice for teams already using Jira or Jira Product Discovery to collect feedback, share roadmaps, and publish release notes. UserVoice suits product organisations that need enterprise feedback programmes with account, segment, and revenue context for prioritisation.
Released Hub Best for teams already using Jira or Jira Product Discovery
UserVoice Best for customer intelligence at enterprise scale
✓ Supported · — Partially supported · × Not available.
| Feature | Released Hub | UserVoice |
|---|---|---|
| Pricing | ||
| Free plan and limits Compare the limits and scope of the free offering. | Supported Up to 10 Jira users | Not available |
| Starting paid price Compare the entry paid plan, billing unit, and payment commitment. Free-plan limits are listed separately. | Standard: $1.10/Jira user/month; volume discounts apply | Not available |
| Pricing model Understand what drives the bill, such as seats, site size, or tracked users. | Released Hub licensing is based on active licensed users on the Jira Cloud site, rather than just the authors using Released Hub. | UserVoice says pricing scales with feedback volume, tools, and connected integrations rather than team seats. |
| Feedback collection and organisation | ||
| Feedback collection Collect ideas, requests, and problems from customers. | Supported | Supported |
| Feedback triage Review incoming feedback and organise it for follow-up. | Supported | Supported |
| End-user feedback portal Give customers a dedicated place to submit and browse feedback. | Supported | Supported |
| Respond to feedback Respond to customers and continue the feedback conversation. | Supported | Supported |
| Reply to feedback directly by email Record a customer’s email reply in the feedback thread without requiring a portal visit. | Supported | Not available |
| Feedback visibility controls Control whether feedback is private or visible to other customers. | Supported | Supported |
| Dedicated feedback forms Collect feedback through a dedicated form embedded in a website or app. | Supported Advanced plan | Not available |
| Automatic feedback capture Extract feedback from connected conversations without manually creating each entry. | Not available | Not available |
| Comments and discussions Discuss a request and add context in a shared conversation. | Supported | Supported |
| Private internal notes Keep team discussion separate from customer-visible replies. | Supported | Supported |
| Prioritisation and customer context | ||
| Wishlists and customer voting Understand which requests matter to customers through votes or personal selections. | Supported | Supported |
| Personal customer wishlists Let customers maintain a personal selection of the features they want. | Supported | Not available |
| Configurable wishlist limits Limit customer selections so they must choose what matters most. | Supported | Not available |
| Hide demand counts Hide totals to reduce the influence of other customers’ choices. | Supported | Not available |
| Customer segmentation Analyse feedback from particular customer groups. | Not available | Supported |
| Revenue-based prioritisation Consider account revenue when assessing customer demand. | Not available | Supported |
| Custom scoring frameworks Score requests using criteria chosen by the team. | Supported Through Jira/JPD | Supported |
| Prioritisation models Use formulas such as RICE or impact versus effort to compare priorities. | Supported Through Jira/JPD | Supported |
| Roadmap views and sharing | ||
| Public roadmaps Share upcoming work and progress with customers or stakeholders. | Supported | Supported |
| Board roadmap view Organise roadmap items into columns by status or planning stage. | Supported | Supported |
| Timeline view Show planned work against dates on a timeline. | Supported | Not available |
| Roadmaps across multiple projects Bring work from multiple projects into one shared roadmap. | Supported | Supported |
| Advanced roadmap filtering Choose which work appears using filters or advanced queries. | Supported | Supported |
| Separate customer-facing descriptions Write a customer-facing explanation separately from the internal planning description. | Supported | Not available |
| Show planning fields on the public roadmap Choose which internal planning fields customers can see on published items. | Supported | Not available |
| Control over roadmap publishing Decide when internal changes become visible to customers. | Supported | Supported |
| Release communication | ||
| Release notes Publish updates that explain what has changed in the product. | Supported | Not available |
| Release-note drafting workflow Compare where AI drafting happens and how source material reaches the writer. | Built-in AI drafting from selected Jira work | Not available |
| Reusable release-note templates Reuse an agreed structure when preparing each product update. | Supported | Not available |
| Configurable AI writing instructions Guide generated writing with tone, examples, or custom instructions. | Supported | Not available |
| Embedded product updates Show product updates directly inside a website or application. | Supported | Not available |
| Changelog email subscriptions Let readers subscribe to product updates by email. | Supported | Not available |
| Shipment communication Tell customers when new work becomes available. | Supported | Supported |
| Request-specific status notifications Notify people about progress on the particular requests they follow. | Not available | Supported |
| Integrations | ||
| Website and app embeds Bring customer-facing content into an existing website or application. | Supported | Not available |
| Support tool integrations Bring feedback from support conversations into the product workflow. | Supported Native through Jira | Not available |
| Team chat integrations Connect team chat to feedback collection or notifications. | Supported | Not available |
| Publishing integrations Distribute product updates to other tools and channels. | Limited Through embeds | Not available |
| API and webhooks Read or update data programmatically and react to product events. | Not available | Supported |
| Access and administration | ||
| Audience controls Choose which customers, teams, or individuals can access shared content. | Supported | Supported |
| External customer participation Let customers contribute without requiring an internal team licence. | Supported | Supported |
| Custom domains Publish customer-facing content under a domain your organisation controls. | Supported | Supported |
| SOC 2 compliance Assess the product’s documented SOC 2 compliance status. | Supported | Not available |
| Single sign-on Let users sign in through an existing identity provider. | Not available | Supported |
| Team roles and permissions Assign team members different responsibilities and access levels. | Not available | Supported |
| Jira integration | ||
| Jira issue linking Associate customer requests with Jira work items, including linking restrictions. | Supported | Supported |
| Jira status sync for linked ideas Keep connected ideas or roadmaps aligned with Jira status changes. | Supported Controlled publishing | Limited Jira and UserVoice statuses are visible across the link but changing one does not automatically change the linked object’s status. |
| Show feedback on Jira work items Review customer feedback from a Jira work item rather than searching another tool. | Supported | Supported |
| Create insights in Jira Product Discovery Create customer insights on Jira Product Discovery ideas. | Supported | Not available |
| Release notes from Jira work Use selected Jira work as the source for release-note drafts. | Supported | Not available |
| Atlassian user management Compare how team access is managed alongside Atlassian accounts and permissions. | Uses Jira permissions | UserVoice uses separate Discovery administration and licences alongside Jira integration permissions. |
Released Hub 
Released Hub is particularly strong when delivery work already lives in Jira. Its AI drafts use selected work items as source material, while templates and writing instructions provide a consistent structure and style for updates.
Released Hub separates internal planning changes from customer-facing updates. Roadmap data stays connected to Jira, while teams decide when changes are ready to share—a useful fit for teams that need to review plans before communicating them.
Personal wishlists, configurable limits, and hidden counts encourage customers to make deliberate choices about the features they want.
Bring customer feedback into Jira Product Discovery as insights, keeping customer input alongside the ideas your team evaluates.
UserVoice 
Analyse demand by customer segment, account attributes, MRR, and revenue.
Create custom feature scores from business criteria, effort, user data, and segments.
Run authenticated forums with ideas, voting, comments, subscriptions, and internal contributors.
Released Hub UserVoice Look beyond vote totals to understand which requests matter, who needs them, and how they inform priorities.
Scoring and prioritisation use the capabilities of Jira and Jira Product Discovery, including custom formulas such as RICE in JPD.
Personal wishlists offer configurable selection limits and hidden counts, encouraging customers to choose what matters most. Why personal wishlists work better than public voting.
Premium supports custom feature fields and formulas using customer segments, effort, and business criteria. Premium segmentation filters demand by user and account attributes such as plan, location, and target market. Teams can analyse ideas and features by MRR, revenue, and high-paying customer segments.
Look at how feedback connects to Jira work and what your team needs to manage across the two tools.
Feedback on a roadmap item links automatically to its Jira work item, keeping customer input connected to the work being discussed. Teams can also link general feedback from the inbox. Jira-connected roadmaps retain control over when updates are shared publicly.
Ideas and Features can link to existing Jira issues or create a pre-populated Jira issue. Jira and UserVoice statuses are visible across the link but changing one does not automatically change the linked object’s status.
Compare the context customers can see and the control your team has over sharing plans and progress.
Board and timeline views turn Jira-connected plans into customer-facing roadmaps. Teams choose which planning fields to display and can write a separate public description for each item.
Jira data stays current in the backend, while the team controls which updates reach customers and stakeholders, and when they are shared.
Discovery Premium provides shareable product roadmaps connected to Features and Ideas. Roadmaps default to admins only and can be shared with contributors, company domains, or external audiences. Discovery Premium supports up to ten additional roadmaps and a combined view across them.
Consider how easily customers can share feedback and continue the conversation with your team.
A shared inbox brings feedback threads, search, workspace/status filters, and keyboard shortcuts into one place. Replies stay in the original thread, keeping each conversation and its context together.
UserVoice centralises, de-duplicates, categorises, filters, and analyses feedback. UserVoice collects feedback directly from end users and through sales, support, and internal teams.
Documentation reviewed 2026-09-15 / 2026-09-16. Based on product documentation and pricing sources.
Reviewed by Jens Schumacher
Last updated:
For teams already using Jira or Jira Product Discovery, Released Hub connects customer feedback, public roadmaps, and release notes with the work they already manage.
