Aha! Roadmaps vs 
Jira Product Discovery Aha! Roadmaps suits product organisations that want customer feedback, prioritisation, and cross-product planning in a dedicated system. Jira Product Discovery suits teams prioritising product ideas in the Atlassian ecosystem. Its public sharing is limited to read-only views: visitors cannot submit feedback or vote without being invited as contributors.
Aha! Roadmaps Best for structured product planning and customer feedback
Jira Product Discovery Best for evidence-based discovery connected to Jira
✓ Supported · — Partially supported · × Not available.
| Feature | Aha! Roadmaps | Jira Product Discovery |
|---|---|---|
| Pricing | ||
| Free plan and limits Compare the limits and scope of the free offering. | Not available 30-day trial | Supported Up to three creators |
| Starting paid price Compare the entry paid plan, billing unit, and payment commitment. Free-plan limits are listed separately. | From $59/user/month, billed annually. Ideas Advanced adds $20/user/month. | 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. | Paid internal users; unlimited portal participants. | 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 Dynamic forms: Ideas Advanced add-on | Limited Collect requests through an embedded Jira Service Management widget. |
| Automatic feedback capture Extract feedback from connected conversations without manually creating each entry. | Supported Ideas Advanced add-on | 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. | Limited My votes view; no separate wishlist | Not available |
| Configurable wishlist limits Limit customer selections so they must choose what matters most. | Limited Vote budgets, rather than wishlist limits | Not available |
| Hide demand counts Hide totals to reduce the influence of other customers’ choices. | Limited Through custom CSS | Not available |
| Customer segmentation Analyse feedback from particular customer groups. | Supported Ideas Advanced add-on | Not available |
| Revenue-based prioritisation Consider account revenue when assessing customer demand. | Supported Ideas Advanced add-on | Not available |
| Custom scoring frameworks Score requests using criteria chosen by the team. | Supported | Supported |
| Prioritisation models Use formulas such as RICE or impact versus effort to compare priorities. | Supported | Supported |
| Roadmap views and sharing | ||
| Public roadmaps Share upcoming work and progress with customers or stakeholders. | Supported Portal pages: Ideas Advanced add-on | 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. | Not available | Not available |
| Show planning fields on the public roadmap Choose which internal planning fields customers can see on published items. | Supported Portal pages: Ideas Advanced add-on | 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. | An AI request summarises a release or selected features into release notes. | Not available |
| Reusable release-note templates Reuse an agreed structure when preparing each product update. | Supported Through note templates | 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. | Not available | Not available |
| Changelog email subscriptions Let readers subscribe to product updates by email. | Not available | Not available |
| Shipment communication Tell customers when new work becomes available. | Supported Portal announcements: Ideas Advanced add-on | Not available |
| Request-specific status notifications Notify people about progress on the particular requests they follow. | Supported | Not available |
| Integrations | ||
| Jira integration Connect customer feedback and plans to delivery work in Jira. | Supported | Supported |
| 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 Ideas Advanced add-on | 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 Portal notes; Ideas Advanced add-on | Limited Embed discovery roadmaps in Confluence pages. |
| API and webhooks Read or update data programmatically and react to product events. | Supported | 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 Ideas Advanced add-on | Limited Premium includes custom domains for the Atlassian app. |
| SOC 2 compliance Assess the product’s documented SOC 2 compliance status. | Not available | Supported |
| Single sign-on Let users sign in through an existing identity provider. | Supported | Not available |
| Team roles and permissions Assign team members different responsibilities and access levels. | Supported Custom roles: Enterprise+ | Supported |
Aha! Roadmaps 
Portfolio views combine releases from multiple workspaces, making Aha! useful when planning spans several products.
Custom scorecards and vote budgets support deliberate prioritisation. Customer segmentation adds further context with Ideas Advanced.
Two-way field and status mappings connect Aha! planning records to Jira delivery work. Direct idea linking is available through the Ideas Advanced add-on.
AI summarises Aha! features and requirements into release notes, with audience and style instructions. Ideas Advanced lets teams publish announcements within the customer portal.
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.
Aha! Roadmaps Jira Product Discovery Compare the context customers can see and the control your team has over sharing plans and progress.
Custom roadmaps let teams choose displayed fields and share the resulting view as a webpage. Published portal roadmaps follow changes to their underlying data.
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.
Custom scorecards support prioritisation factors such as RICE. Ideas Advanced adds customer segmentation and revenue analysis using connected CRM account and opportunity data, allowing priorities to reflect customer groups and commercial context alongside idea scores.
Build custom prioritisation formulas with roll-ups, weighted scores, and expressions.
Consider how easily customers can share feedback and continue the conversation with your team.
Teams can review incoming ideas, assign statuses, and respond through portal comments or official admin responses. Portal settings control idea visibility and private comments. Submit-only portals collect feedback without browsing or voting; dynamic multi-step forms require Ideas Advanced.
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.
Look at how feedback connects to Jira work and what your team needs to manage across the two tools.
Aha! Roadmaps supports two-way Jira synchronisation with configurable field mappings and update direction. Linking ideas directly and syncing their statuses requires Ideas Advanced and a separate integration configuration. Users and workspace permissions remain administered in Aha! rather than inherited from Jira.
Create or link Jira delivery work from an idea and monitor delivery progress.
Documentation reviewed 2026-09-16 / 2026-09-18. Based on product documentation and pricing sources.
