Released Hub vs 
Jira Product Discovery Jira Product Discovery helps your team decide what to build. Released Hub adds a branded place for customers to share feedback, follow selected roadmap items, and read release notes. Use them together to keep discovery and customer communication connected.
Released Hub Best for teams already using Jira or Jira Product Discovery
Jira Product Discovery Best for evidence-based discovery connected to Jira
✓ Supported · — Partially supported · × Not available.
| Feature | Released Hub | Jira Product Discovery |
|---|---|---|
| Pricing | ||
| Free plan and limits Compare the limits and scope of the free offering. | Supported Up to 10 Jira users | Supported Up to three creators |
| 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 | Standard starts at US$10 per creator/month; Premium starts at US$25 per creator/month. |
| 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. | Creators are billable; contributors are free and need an Atlassian account. |
| 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 | Limited Public views are read-only; customer request intake requires connected Jira Service Management. |
| Respond to feedback Respond to customers and continue the feedback conversation. | Supported | Limited Continue customer conversations in Jira Service Management when it is used for intake. |
| 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 | Not available |
| Dedicated feedback forms Collect feedback through a dedicated form embedded in a website or app. | Supported Advanced plan | Limited Collect requests through an embedded Jira Service Management widget. |
| 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 | Limited Keep internal notes separate from customer replies on connected Jira Service Management requests. |
| Prioritisation and customer context | ||
| Wishlists and customer voting Understand which requests matter to customers through votes or personal selections. | Supported | Limited Invited contributors can vote on ideas; published views do not support voting. |
| 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 | Not available |
| Revenue-based prioritisation Consider account revenue when assessing customer demand. | Not available | Not available |
| 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 Standard or Premium |
| 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 | Supported |
| Roadmaps across multiple projects Bring work from multiple projects into one shared roadmap. | Supported | Supported Premium |
| Advanced roadmap filtering Choose which work appears using filters or advanced queries. | Supported | Limited Published-view readers can filter and sort; some field types cannot be used for publishing. |
| 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 | Limited Choose published fields and descriptions; votes, formulas, and some other fields are unsupported. |
| Control over roadmap publishing Decide when internal changes become visible to customers. | Supported | Limited Publish or unpublish live views; source changes remain visible without a separate publishing approval. |
| 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 | Not available |
| Request-specific status notifications Notify people about progress on the particular requests they follow. | Not available | Not available |
| Integrations | ||
| Website and app embeds Bring customer-facing content into an existing website or application. | Supported | Limited Embed a connected Jira Service Management request widget in a website or app. |
| Support tool integrations Bring feedback from support conversations into the product workflow. | Supported Native through Jira | Supported |
| Team chat integrations Connect team chat to feedback collection or notifications. | Supported | Supported |
| Publishing integrations Distribute product updates to other tools and channels. | Limited Through embeds | Limited Embed discovery roadmaps in Confluence pages. |
| API and webhooks Read or update data programmatically and react to product events. | Not available | Not available |
| 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 | Limited External participants can contribute when invited with an Atlassian account and appropriate permissions. |
| Custom domains Publish customer-facing content under a domain your organisation controls. | Supported | Limited Premium includes custom domains for the Atlassian app. |
| SOC 2 compliance Assess the product’s documented SOC 2 compliance status. | Supported | Supported |
| Single sign-on Let users sign in through an existing identity provider. | Not available | Not available |
| 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 Track progress from linked Jira work through the delivery progress field. |
| Show feedback on Jira work items Review customer feedback from a Jira work item rather than searching another tool. | Supported | Not available |
| Create insights in Jira Product Discovery Create customer insights on Jira Product Discovery ideas. | Supported | Supported |
| 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 | Manage creators, contributors, and space permissions through Atlassian access and roles. |
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.
Jira Product Discovery 
Capture supporting evidence and rate its impact before deciding what to build.
Link prioritised ideas to Jira work and follow delivery progress from discovery.
Public sharing provides read-only discovery views. Visitors can browse, filter, and sort ideas, but cannot submit feedback or vote. Participation needs an invited Atlassian account or a connected Jira Service Management portal. Published views also exclude votes, custom formulas, and insight counts.
Product Collection’s Feedback app and Rovo workflows are available through a separate early access program requiring Jira Product Discovery Premium. These comparisons cover standalone Jira Product Discovery.
Released Hub Jira Product Discovery Compare the context customers can see and the control your team has over sharing plans and progress.
Teams choose the Jira fields customers see and write a separate public description for each roadmap item. This creates a customer-facing view with the planning context the team wants to share.
Jira data remains current in the backend, with control over when updates are published to stakeholders and customers.
Jira Product Discovery’s public sharing is limited to read-only views. Visitors can browse, filter, and sort ideas, but cannot submit feedback or vote.
Teams can choose which supported fields and descriptions appear, but votes, reactions, custom formulas, and insight counts cannot be published. Customer participation needs invited contributor access or a connected Jira Service Management portal.
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.
Build custom prioritisation formulas with roll-ups, weighted scores, and expressions.
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.
Link discovery ideas to existing Jira work items or create new delivery work.
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.
Organise insights with labels and impact ratings, then use that evidence to prioritise ideas.
Public views are read-only. Collecting customer requests and continuing conversations requires invited contributor access or a connected Jira Service Management setup.
Keep discovery in JPD and give customers a clear place to participate. Explore how the workflow connects.
Keep capturing ideas, gathering evidence, and scoring priorities in Jira Product Discovery. Released Hub gives customers and stakeholders one place to share feedback, follow your roadmap, and read release notes.
Don’t make stakeholders chase links. Bring your roadmap, feedback, and product updates together in a branded portal. Choose public access or restrict the portal to the audience you want to reach.
Tailor the roadmap to customers, sales, or leadership so each audience can see what matters to them without navigating the internal Jira workspace. Keep the public view connected to selected Jira work items and JPD ideas.
Customers and stakeholders can comment on roadmap items and submit feedback on ideas. That gives them a direct way to explain what they need and continue the conversation with your team.
Review feedback from your portals in one inbox, organise the conversations, and connect them to the relevant Jira work item or JPD idea. Replies stay with the feedback, keeping the customer’s context close to the work.
Feedback can become insights on the connected JPD idea. Authenticate the Jira Product Discovery connection in feedback settings first; incoming feedback can then reach discovery without copying each comment by hand.
Each customer can curate a personal wishlist of roadmap items. Set a selection limit to encourage deliberate choices and keep wish counts hidden from customers to reduce the influence of other people’s votes. Your team can use those signals alongside the evidence in JPD.
Product communication often spans several teams. Connect work from Jira Software, Jira Product Discovery, and Jira Service Management projects, then choose what to share in the portal. The roadmap stays close to the work your teams already manage.
Use themes, colours, and customer-facing descriptions to make the roadmap clear and recognisable. Publish on a custom subdomain or embed the portal in your website or app so customers can find it where they already spend time.
When work ships, turn the relevant Jira work items into a release-note draft. Use the AI copywriter for the first pass, then focus your editing on the customer benefit and the story behind your headline features. Review the update before publishing it through your portal or other release-note channels.
Sharing plans, collecting feedback, and keeping customers informed.
Jira Product Discovery is where product teams capture evidence, prioritise ideas, and connect planned work to delivery. Released Hub adds a branded place to collect customer feedback, share selected roadmap items, and publish release notes. Teams can use both together.
JPD supports published views and contributor participation, and can collect requests through a connected Jira Service Management portal. Released Hub adds a branded product portal where customers can submit feedback, comment on roadmap items, and maintain personal wishlists without access to your internal planning space.
No. Released Hub also works with Jira Software. Share selected Jira work through a customer-facing roadmap and release notes, then add JPD when you need a dedicated discovery and prioritisation workflow.
JPD can publish views for people outside your team when your plan, permissions, and site settings allow it. For a branded portal that also collects feedback and publishes release notes, use Released Hub to choose which Jira or JPD items customers see and how those items are presented.
Yes. People with access to your Released Hub portal can submit feedback and comment on roadmap items without access to the internal Jira project. Your team can link that feedback to the relevant Jira work item or JPD idea.
Released Hub can draft release notes from the relevant Jira work. When delivery work connected to a JPD idea is complete, select the items that belong in the update and use the draft as the starting point for your customer-facing story. Your team reviews and publishes the update.
Atlassian’s published-view documentation describes sharing and access controls but does not document a view-visit counter. If visit measurement is a requirement, confirm the available analytics before choosing a publishing approach. Released Hub’s portal access, branding, and feedback features are separate from measuring visits to a JPD view.
Documentation reviewed 2026-09-15 / 2026-09-18. Based on product documentation and pricing sources.
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.
