I love the Jira integration because it directly connects priorities on the roadmap to delivery work, eliminating any context loss between discovery and execution. The flexibility of custom fields and multiple views is a big win, allowing us to easily tailor prioritization frameworks, like RICE, to meet our team's needs. It's great that everyone from engineering, product managers, to executives can view the same data in formats that work for them, removing the need to maintain separate decks. Being purpose-built for product teams, it just clicks in a way generic project tools don't. The project templates make getting up and running quickly smooth, especially if you're already familiar with the Jira ecosystem. Review collected by and hosted on G2.com.

The biggest gap is external feedback - there's no way for customers to submit ideas or vote directly, so we're manually collecting and inputting everything. Reporting is also quite basic, and there's no mobile experience worth mentioning. Review collected by and hosted on G2.com.

I use Jira Product Discovery for centralizing ideas and insights, which serves as a single, centralized intake funnel for me. I like that it replaces rigid timelines with dynamic, outcome-based roadmaps. Because it is natively built into Jira, these roadmaps are living documents, and when engineering updates a ticket in Jira Software, the status automatically reflects on the Jira Product Discovery strategic roadmap. It's pretty easy to set up. Review collected by and hosted on G2.com.

Jira Ecosystem Lock-in: if your engineering team doesn't use Jira Software for delivery, Jira Product Discovery loses its biggest competitive advantage. Review collected by and hosted on G2.com.

I use Jira Product Discovery in my work environment because it makes it much easier to track and visualize tasks across different teams. It helps solve the chaos of prioritization, allowing me and my team to avoid wasting hours in meetings arguing about priorities. I appreciate having a single place to capture customer requests, score them by effort and value, and eliminate low-impact ideas before they consume development time. I like the organization and ranking efforts, which have helped improve our team communication. The tool's ability to provide visualization and tracking of impacts is very valuable, as it lets us know exactly where our efforts are going. Additionally, the initial setup was really easy thanks to Jira's plethora of templates and documentation. Review collected by and hosted on G2.com.

A live chat between coworkers where we could discuss tasks would be nice. We could ping coworkers based on a job thread to discuss changes about the task. Oh, and also that, maybe a feature where we could see the changes happening on a job. Review collected by and hosted on G2.com.

What I like most about Jira Product Discovery is how it helps teams organize ideas, prioritize opportunities based on impact, and make product decisions transparently. It keeps product discovery structured, while still making it easy to collaborate with stakeholders and maintain a clear, shared roadmap. Review collected by and hosted on G2.com.

I don’t have any major complaints. A few of the more advanced customization options could be a bit more flexible, but overall the experience feels intuitive and works well for discovering products. Review collected by and hosted on G2.com.

Discovery is how it brings product thinking and execution into one place. It makes it easy to capture ideas, prioritize them based on impact, and align them with business goals.

I especially appreciate the flexible prioritization frameworks (like impact vs effort), which help in making data-driven decisions instead of relying on assumptions. The custom fields and views allow teams to tailor workflows based on their needs, whether it’s roadmap planning or backlog refinement.

Another big advantage is its seamless integration with Jira Software, which ensures a smooth transition from idea to development without losing context. This improves collaboration between product, engineering, and stakeholders. Review collected by and hosted on G2.com.

One thing I dislike about Jira Product Discovery is that it still feels a bit limited compared to more mature product management tools. While it’s great for idea tracking and prioritization, some advanced features—like deeper analytics, dependency mapping, or more structured roadmapping—can feel basic.

Another challenge is the learning curve, especially for new users who are not already familiar with the Atlassian ecosystem. Setting up views, fields, and workflows can take time to get right.

Also, while integration with Jira Software is useful, it’s not always as seamless as expected—sometimes there’s a gap between high-level product ideas and detailed engineering tasks. Review collected by and hosted on G2.com.

I like how simple Jira Product Discovery makes idea management and appreciation. You can quickly capture ideas, add insights, and score them based on impact, effort, or business value without overcomplicating the process. The flexibility in customizing fields and views helps it adapt to different teams and use cases. Another strong point is its connectivity with the rest of the Atlassian ecosystem, especially Jira, which makes it easy to move from idea to delivery without losing context. It also improves collaboration by giving stakeholders clear visibility into why certain ideas are prioritized over others. Review collected by and hosted on G2.com.

One area that could be improved in Jira Product Discovery is the level of reporting and analytics. While it's great for capturing and prioritizing ideas, the built-in reporting is still quite basic. More advanced, concise, and customizable dashboards would help in tracking trends and presenting data to stakeholders more effectively. Additionally, although it offers flexibility with fields and views, certain workflows and automations are not as advanced as what you get in Jira, which can be slightly restrictive for teams that want more complex idea lifecycle management. Collaboration features could also be enhanced; while sharing and commenting is possible, real-time collaboration and structured feedback collection from stakeholders, especially in larger teams, could be improved. In terms of integration, even though it connects well with Atlassian tools, integrations with non-Atlassian tools could be smoother and more extensive. A suggestion would be to enhance reporting capabilities, expand automation and workflow options, and improve collaboration and third-party integrations to make it more robust for end-to-end product discovery. Review collected by and hosted on G2.com.

What I like most about Jira Product Discovery is how simple and structured it makes idea prioritization. It's very easy to capture ideas, add context, and score them based on impact and effort. I also like the transparency it provides. Everyone can see why a particular idea is prioritized, which really helps with alignment across teams. Overall, it keeps discovery organized without adding too much process. Review collected by and hosted on G2.com.

One area where Jira Product Discovery could improve is reporting analytics. While prioritization is clear, getting detailed insights on custom reports sometimes feels limited. Also, for teams that are new to product discovery, there can be a bit of a learning curve to fully understand scoring and configuration. Better out-of-the-box guidance and deeper integrations could make it even more powerful. Review collected by and hosted on G2.com.

What distinguishes Jira Product Discovery is its systematic approach to idea generation and management that covers the whole journey from collecting ideas to prioritizing those that have the greatest value. As opposed to a set of random inputs that can come from anywhere, the solution helps collect all ideas in one place in order to facilitate evaluation and further refinement.

One of the main strengths of Jira Product Discovery is the opportunity to prioritize and evaluate ideas based on any criteria such as impact, effort, strategic fit, and importance for customers. This means that the prioritization process becomes more systematic and based on measurable criteria. One can develop a scoring matrix to help understand the value of different opportunities.

Moreover, this tool encourages collaboration across different roles and departments in order to improve product development processes. All team members, including product managers, designers, developers, and leaders, can share one product discovery board in which they collaborate. Roadmaps and views can be adjusted to cater to specific audiences. Review collected by and hosted on G2.com.

My main complaint about Jira Product Discovery lies in the fact that even though it provides excellent means for organizing ideas, it can sometimes be slightly restricting regarding customization and more complex workflows. It might not be the best choice for more experienced product development teams who need more sophisticated tools to manage their products.

The user interface is quite good and easy on the eyes, yet learning it properly may require additional time. The collaborative functionality is helpful, but it still has room for improvement. Review collected by and hosted on G2.com.

The most valuable aspect of Jira Product Discovery is its seamless integration with existing Jira workflows, allowing our product team to prioritize features based on real customer feedback and data-driven insights. The idea management capabilities have significantly streamlined how we collect, evaluate, and prioritize product opportunities. The visual roadmapping features make it easy to communicate our product strategy to stakeholders across the organization, and the ability to link ideas directly to development work in Jira Software creates excellent traceability. The collaboration features enable cross-functional teams to contribute insights and vote on priorities, which has improved our decision-making process considerably. Review collected by and hosted on G2.com.

While the tool is powerful, there is a learning curve for new users, especially those not familiar with the Jira ecosystem. The initial setup and configuration can be time-consuming, requiring careful thought about custom fields and workflows. Some advanced filtering and reporting features could be more intuitive - it sometimes takes several clicks to create complex views. The mobile experience is limited compared to the desktop version, which can be challenging for teams that work remotely or travel frequently. Additionally, the pricing structure can be a barrier for smaller teams or startups. It would be beneficial to have more pre-built templates for common use cases to help teams get started faster. Review collected by and hosted on G2.com.

Its how effectively it helps organize and priortize and manage product ideas in a collaborative and structured way. The platform provides a clean and intuitive interface that makes it easier for teams to capture feedback, evaluate opportunities and align product decisions with business goals Review collected by and hosted on G2.com.

Some advanced customization and reporting capabilities can feel limited compared to more mature product management platforms.

I also felt new users can have some learning curve Review collected by and hosted on G2.com.