Jira Product Discovery Reviews & Product Details

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.

What I like best is having ideas, customer feedback, and priorities in one place instead of scattered across spreadsheets. Custom scoring fields help us rank ideas objectively, and since it's built on Jira, we can move ideas straight into delivery and track their progress. Sharing roadmaps with stakeholders is quick and easy too. Review collected by and hosted on G2.com.

The initial setup takes some effort, since fields, views, and scoring formulas need to be configured before it really fits your workflow. Getting stakeholders who aren't familiar with Jira comfortable with it can also take time. I'd love to see a mobile app and more automation for categorizing incoming ideas. 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.

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.

Jira Product Discovery makes it easy to capture ideas, prioritize them, and collaborate with the team. I like that it connects product planning directly with Jira Software, so moving from an idea to implementation is straightforward. The interface is clean, and the custom views help track priorities without adding unnecessary complexity. Review collected by and hosted on G2.com.

The biggest drawback is the initial learning curve. While it's powerful, it takes some time to understand all the features and configure them effectively. I also wish there were more customization options for views and reporting, and the pricing may be a bit high for smaller teams. Review collected by and hosted on G2.com.

It’s really easy to use. The simple, intuitive design makes it quick to understand, unlike some other project management tools. And if you’re an advanced user, you can still use Jira’s Marketplace Apps without spending ten thousand hours figuring everything out.

That said, some screens take a while to load. It’s not as fast as Trello, and there’s definitely more loading time compared to Trello (which feels instant). On the other hand, it’s also more advanced than Trello. I think at least some of that loading comes from how extremely customizable the spaces are. Every time you create a new space, you can tailor the entire workflow, and the onboarding process gives you solid, high-level control over how you want to manage projects philosophically.

Even if you don’t pay and stick with the free plan, you still get more features than you typically do with an average PM tool, so it’s worth giving it a shot. Review collected by and hosted on G2.com.

The load times are frustrating. There were countless times when I had to refresh the browser because it got stuck during the onboarding flow.

Also, if you’re feeling lazy, you might not find any useful AI features. It would be great if I could use AI to quickly create the perfect space for me based on my past usage patterns, personal choices, and workflow. Review collected by and hosted on G2.com.

I like that Jira Product Discovery allows me to decouple 'ideation' from 'execution,' simplifying the process by using customizable scoring formulas to balance security impact with engineering capacity. Its direct linking of 'Insights' from stakeholders to our Azure DevOps backlog ensures data-driven decision-making for our infrastructure roadmap. I appreciate the custom prioritization frameworks, which help balance technical debt against business value. The Published Views feature has improved our stakeholder management, enabling a 'pull' model for real-time visibility into our Azure strategy while keeping the engineering team focused. Integration with tools like Azure DevOps, Microsoft Teams, and Qualtrics enhances its functionality, supporting a seamless 'Digital Thread' from our strategic roadmap to technical delivery. The technical setup was seamless with our existing Atlassian and Entra ID stack, making the implementation smoother and more efficient. Review collected by and hosted on G2.com.

The biggest hurdle is the siloed nature of the feedback loop. While it's excellent for internal prioritization, it lacks a native public-facing portal for broader stakeholder engagement. Additionally, for teams in a hybrid environment, the Azure DevOps sync still has minor latency that requires manual oversight. I’d like to see more conditional logic in the scoring formulas so we can automate our risk-based prioritization more effectively. Review collected by and hosted on G2.com.