I haven’t used it as extensively as Jira Software, but I have used it to get visibility into upcoming features, product ideas, and how different initiatives are being prioritized. It gives me a much clearer picture of what’s being planned before development even starts.

What I like most is that everything is organized in one place. Rather than having feature requests scattered across emails and separate documents, the ideas, comments, priorities, and supporting context are all available together. As someone on the QA team, this helps me understand the reasoning and background behind a feature before it ever reaches the sprint.

It’s also helpful that it connects well with the Atlassian ecosystem, so moving from an approved idea to actual development work feels natural and straightforward. Review collected by and hosted on G2.com.

Since my role isn’t in product management, I don’t regularly use all of the tool’s capabilities. When you’re using it for the first time, it also takes a bit of time to understand how ideas, fields, and views are structured and how everything fits together.

Other than that, I don’t have any major concerns. Most of the complexity is in the initial learning curve rather than in day-to-day use. Review collected by and hosted on G2.com.

What I like most about Jira Product Discovery is that it keeps product ideas, feedback, and priorities in one place. It’s easy to capture new ideas quickly, discuss them with the team, and decide what’s actually worth building. The different views make roadmaps and priorities easy to understand, even for people outside the product team. It feels much lighter and easier to work with than standard Jira projects for early-stage planning. Review collected by and hosted on G2.com.

One thing I dislike about Jira Product Discovery is that some of the customisation options are still fairly limited, especially when trying to tailor views and fields for more complex product workflows. Review collected by and hosted on G2.com.

I like most about Jira Product Discovery is how it brings product ideas, feedback, and prioritization into one place. As someone working in B2B marketing, I find it useful for understanding the rationale behind product decisions and staying aligned with product and engineering teams. The customizable fields, prioritization frameworks, and roadmap views make it easier to track initiatives and communicate priorities across stakeholders. Since it integrates seamlessly with Jira Software, the transition from idea to execution is smooth, which helps improve cross-functional collaboration and visibility. Review collected by and hosted on G2.com.

One area where Jira Product Discovery could improve is the learning curve for new users. While it's highly customizable, setting up projects, views, and prioritization frameworks can take some time. I also feel that some reporting and visualization features could be more flexible, especially for sharing executive-level updates with non-technical stakeholders. Additionally, as the volume of ideas grows, organizing and navigating them can become a bit challenging without a well-defined structure. Overall, these are usability improvements rather than major limitations, and the platform continues to be valuable for product planning and collaboration. Review collected by and hosted on G2.com.

At LocalConnect, we use Jira Product Discovery to collect customer feedback, create idea records, and prioritize feature requests before each release. I like how custom fields and prioritization make it easy to compare ideas based on customer impact and business value. Once an idea is approved, we link it directly to Jira Software so the development team can start implementation without duplicating work. The integration with Figma also helps us review designs while discussing new features, making product planning much more organized and collaborative. Review collected by and hosted on G2.com.

While Jira Product Discovery is very useful overall, some advanced roadmap views and customization options are only available in higher plans, which can be limiting for smaller teams. When managing a large number of ideas, the workspace can sometimes feel slower, making it take longer to review and prioritize features during planning sessions. I would also like more flexible dashboard customization and reporting so it's easier to share product updates with different stakeholders. Review collected by and hosted on G2.com.

First, you’ll love that you can make your own fields and view types without having to use spreadsheets outside of the product, such as creating “Now/Next/Later” roadmaps, impact-effort matrices, etc. This saves a lot of time because all those things are typically created using spreadsheets.

Secondly, if you’re already using Atlassian’s software suite, including Jira Software for ticket tracking, then integrating Backlog into your process will be easy. You can easily connect discovery ideas to delivery tickets in Jira. As an example, I’ve used Jira since 2013 on various projects at my company, but didn’t start working in backlog until recently – now that I’ve started using backlog, everything connects together nicely and creates a more streamlined flow from ideation through execution. Review collected by and hosted on G2.com.

Idea’s biggest problem for us though is being able to connect ideas to others – there isn’t an option here to create a hierarchy between them, you have to do this with some pretty rudimentary hacks (custom fields). I understand why they’ve done things this way, but this feature shouldn’t be too hard to build and would make a world of difference in making Idea more powerful out-of-the-box. Review collected by and hosted on G2.com.

What I like most about Jira Product Discovery is how it helps me organize ideas, prioritize opportunities, and keep everyone aligned on product decisions. It provides clear visibility into what we’re working on and the reasons behind it, which makes collaboration across the team much smoother and more straightforward. Review collected by and hosted on G2.com.

I don’t have many complaints overall. If I had to point out one thing, it would be that the interface can feel a bit overwhelming at first, especially for new users. That said, once you spend a little time getting familiar with it, it becomes much easier to navigate and use. Review collected by and hosted on G2.com.

What I like most about Jira Product Discovery is how easily it centralizes, prioritizes, and structures all product ideas in one place. It is a key tool for connecting the discovery phase with execution in Jira, helping align teams through visual, transparent roadmaps backed by real data. Review collected by and hosted on G2.com.

What I dislike the most is that the initial learning curve can be somewhat steep for non-technical users. Additionally, I feel that the deep integration with external design tools or documentation repositories still has room for improvement to prevent information duplication. Review collected by and hosted on G2.com.

I really appreciate its seamless connection to the engineering pipeline, unlike traditional product tools that require manual translation of ideas into development tickets. The idea prioritization views are the highlight finally have a structured way to rank what actually matters. UI is clean and intuitive, much lighter than regular Jira which is a relief. Integrations with Jira Software are convenient, keeps product and dev teams aligned without extra tools. Performance is smooth, no complaints there. Onboarding was quick, support docs are solid. AI-driven insights for spotting patterns across customer feedback is a nice touch, saves a lot of manual digging. Talking about the pricing it felt pretty reasonable if youre already a preexisting customer of the atlassian Review collected by and hosted on G2.com.

The prioritization views can feel a bit rigid at times, which makes it difficult to customize the scoring so it truly reflects how our team thinks and evaluates priorities. Review collected by and hosted on G2.com.

What I like most about Jira Product Discovery is how simple it is to capture ideas and turn them into real, actionable tasks. I can add ideas quickly, prioritize them, and link them directly to Jira issues so everything stays organized in one place. The different views, such as boards and roadmaps, also make it easier to share priorities clearly with the team. Overall, it helps keep product planning and execution aligned and in sync. Review collected by and hosted on G2.com.

One downside of Jira Product Discovery is that it still feels a bit basic compared to more established product tools. Some features, like detailed analytics or advanced prioritization options, are quite limited. It can also take some time to understand how everything is set up, especially if you’re new to Atlassian tools. At times, the interface can feel a little slow or clunky when handling a large number of ideas. Review collected by and hosted on G2.com.

What I like best about Jira Product Discovery is how it makes idea prioritization more structured and transparent. Features like Impact Assessment, Impact vs Effort views, and RICE scoring help compare opportunities objectively and focus on initiatives with the highest value. The UI is easy to navigate, and custom views, roadmap, timeline, and delivery status views provide good visibility throughout the lifecycle of an idea. I also like the integration with Jira, which helps maintain context when ideas move into implementation. The AI features are useful for generating and refining idea descriptions, saving time during the discovery process. Review collected by and hosted on G2.com.

Ask Rovo is useful for quickly finding information, summarizing requirements, and generating draft idea descriptions. It helped reduce the time spent manually reviewing discussions and documentation, especially during the early discovery phase. However, for more detailed requirements and AI use cases, I still needed to review and refine the generated content to ensure the business context was captured accurately. Review collected by and hosted on G2.com.