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.

According to me the most helpful features about Jira Product is a simple and easy to capture organise, and prioritise ideas while creating a clear roadmaps and tracking progress.

There pricing is less and ROI is high. Review collected by and hosted on G2.com.

There is not a specific reason of dislike but in the initial stage in jira new users might also findings setups and structuring for further process little bit confusing their support might lacking sometimes.

I suggest you to work in AI / Intelligence integrations solution which help us to improve performance at early stage. Review collected by and hosted on G2.com.

What I like best about Jira Product Discovery is how it helps us bring business requirements, stakeholder feedback, and automation opportunities into one place. Features like Task Ranking make it easier to prioritize ideas based on business value and feasibility, while Custom Workflows allow us to adapt the evaluation process to our team's needs. I also find the integration with Jira valuable because developers can access the complete business context during implementation, reducing back-and-forth discussions and helping us deliver automation and AI projects more effectively. Review collected by and hosted on G2.com.

One area that could be improved is the UI for managing evaluation criteria and prioritization. As the number of factors increases, tracking scores and understanding how priorities are calculated can become difficult. I’d also like more flexibility in customizing and visualizing scoring models for larger automation and AI initiatives. Review collected by and hosted on G2.com.

It offers clear documentation of internal platform improvements, provides everyone with visibility into ongoing progress, and calls out what's at risk. The UI is fast, flawless, and easy to use, so new colleagues begin using it seamlessly from day one of onboarding. Review collected by and hosted on G2.com.

Stakeholders are often confused by having multiple Jira projects as it's difficult to sync ideas between JPD and the Epics in Jira Software. We're using AI to generate all data fields, workflows, and views, but we've found those generated elements to be less customisable than in Jira Software. Review collected by and hosted on G2.com.

As a project analyst who has been using Jira Product Discovery (JPD) for about a year now, what I like best is how it bridges the gap between chaotic ideation and structured execution. Before JPD, my product discovery lived across scattered spreadsheets, Slack threads, and random docs. JPD brings all of that into one centralized sandbox designed specifically for product thinking, not just task tracking. The standout feature for me is the decoupled data structure. I can capture raw ideas, customer pain points, and feedback without cluttering our delivery boards or prematurely committing to a build. It maintains the underlying context, so the engineering team can actually see why we are building something, keeping everyone connected to the bigger picture without any manual duplication of work. It has essentially turned a historically messy process into a transparent, collaborative pipeline. Review collected by and hosted on G2.com.

Honestly, after a year of leaning on JPD, the thing that drives me crazy is how siloed it feels when you scale. While it’s great for a single product line, the moment you try to roll up ideas from multiple JPD projects into one master portfolio view, you hit a wall. There is no easy way to build a centralized matrix to compare priorities across different product lines, forcing you to either cram everything into one massive, chaotic project or deal with data silos. Finally, collaboration with non-product teams is surprisingly high-friction. JPD is built for product managers, but getting sales or customer success to regularly input feedback or vote on ideas is tough because the permission settings are so rigid It’s an incredibly powerful tool for connecting discovery to execution, but it still feels restricted by the rigid, engineering-first constraints of the broader Jira ecosystem. Review collected by and hosted on G2.com.

I use Jira Product Discovery as a central hub to capture, organize, and prioritize product ideas. It bridges the gap between product management and engineering by allowing us to gather feedback from various stakeholders, evaluate impact versus effort, and map high-priority ideas directly to Jira Software epics and user stories. What stands out most is how it brings clarity and structure to feature prioritization. The custom visual roadmaps and impact vs. effort matrix views allow product managers and technical leads to align on what to build next. Stakeholders get full visibility into why certain features are prioritized, and team members can vote or comment on ideas directly. Having all of this live inside the Atlassian ecosystem means developers always have direct visibility into user research and business value behind every ticket. The initial onboarding was very straightforward with Atlassian providing clear templates and default views right out of the box. Review collected by and hosted on G2.com.

I find the distinction between creator, contributor, and viewer slightly confusing initially. Managing access permissions for non-product stakeholders who just want to submit ideas can feel overly complex in the Atlassian admin portal. While engineers and product managers adjust quickly, business or customer-facing teams can find the interface a bit overwhelming compared to simpler dedicated feedback tools. Review collected by and hosted on G2.com.

I use Jira Product Discovery to collect and organize product ideas, feature requests, and feedback, which helps evaluate and prioritize ideas based on business value and impact. The integration with Jira is super, and its flexible roadmap views make it easy to move from planning to execution. I enjoy the seamless connectivity of product ideas with work items, which simplifies tracking progress from start to delivery. The initial setup was straightforward and user-friendly, with a step-by-step guide that was easy to follow. Review collected by and hosted on G2.com.

Overall Jira works well for me but I would like to see more advanced reporting because we would be presenting it to the stakeholders and this would be very beneficial for me. Review collected by and hosted on G2.com.

What I like best is how seamlessly it links our initial brainstorming directly to our delivery team. We can capture user feedback for our community app, score the ideas based on real criteria, and then push the winning concepts straight to our developers without losing any of the original context. Review collected by and hosted on G2.com.

While the platform is incredibly powerful, there is definitely a learning curve for team members who are not already familiar with the broader Atlassian ecosystem. Setting up the initial custom fields and prioritization frameworks exactly how you want them takes some dedicated time and patience before you really see the full value. Review collected by and hosted on G2.com.