Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Difference between JSM & JPD

I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 29, 2024

Pros & Cons between Jira Service Management & Jira Product Discovery

would help if some application is shared

2 answers

Suggest an answer

Log in or Sign up to answer
6 votes
Perisic Nikola
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 1, 2024

Welcome to the community @RAM A !

  • JSM: Resolving customer issues and requests. It helps teams manage service desks, track incidents, and deliver IT support effectively.
  • JPD: Understanding user needs and prioritizing product features. It provides tools to gather insights (like user feedback, research data), prioritize ideas, and build a data-driven product roadmap.
  • JSM: Primarily IT support teams, customer service representatives, and anyone involved in resolving customer issues.
  • JPD: Product managers, product owners, and other stakeholders who need to understand customer needs, prioritize product features, and communicate roadmaps.
  • JSM: Offers features like ticketing system, incident management, service level agreements (SLAs), self-service portal, and reporting.
  • JPD: Provides tools for capturing insights, conducting user research, prioritizing ideas, building roadmaps, and collaborating with stakeholders.
  • JSM can be integrated with JPD to feed insights from customer requests into the product discovery process. This allows teams to identify pain points and potential product improvements based on actual customer experiences.
  • JSM and JPD are complementary products that work together in different stages of the product development cycle. JSM helps ensure existing products function well and meet customer needs, while JPD helps guide the development of future product features that address user problems and opportunities.
3 votes
Denis Paul March 1, 2024

Both tools are catered for different uses. JSM is more for "classic" service management including bugreporting, change requests, incident handling and can even be connected to your infrastructure and devices to connect tickets to devices or servers.

JPD ist meant for product development. You can collect, sort, prioritize and communicate ideas that could be turned into features later.

Of course both tools can be used in different ways and could also do other things as they basically are open ticketing systems with configurable workflows.  

Besides that I totally agree with what ChatGPT says:

Jira Service Management


1. Robust ticketing system: Jira Service Management offers a comprehensive ticketing system to manage and track customer requests and incidents efficiently.
2. Customizable workflows: Users can create custom workflows tailored to their specific business needs, allowing for streamlined processes.
3. Integration with other Atlassian tools: Jira Service Management integrates seamlessly with other Atlassian products like Confluence, Bitbucket, and Jira Software, providing a cohesive ecosystem for project management and collaboration.
4. Service Level Agreement (SLA) management: It provides built-in SLA management features, enabling teams to prioritize and resolve issues based on predefined service level agreements.
5. Knowledge base: Jira Service Management includes a knowledge base where users can access self-help articles and documentation, reducing the volume of support requests.
6. Reporting and analytics: It offers robust reporting and analytics capabilities, allowing teams to track key performance metrics and identify areas for improvement.


1. Steep learning curve: Jira Service Management can be complex for new users, requiring time and effort to fully understand its features and functionalities.
2. Pricing: Depending on the organization's size and requirements, the pricing for Jira Service Management can be relatively high, especially for large teams.
3. Customization limitations: While Jira Service Management allows for customization, some users may find the customization options limited compared to other platforms.
4. Performance issues: In some cases, users have reported performance issues with Jira Service Management, particularly when dealing with large datasets or complex workflows.
5. Dependency on Atlassian ecosystem: Users who are not already using other Atlassian products may find it challenging to adopt Jira Service Management due to its tight integration with the Atlassian ecosystem.

Jira Product Discovery


1. User-friendly interface: Jira Product Discovery offers an intuitive interface designed specifically for product discovery and development teams, making it easier to manage projects and tasks.
2. Agile project management: It supports agile methodologies such as Continuous Discovery, Scrum and Kanban, allowing teams to plan, track, and deliver products iteratively.
3. Roadmap planning: Jira Product Discovery enables teams to create and manage product roadmaps, helping align stakeholders and prioritize features effectively.
4. Collaboration features: It includes collaboration features such as commenting, tagging, and mentions, facilitating communication and teamwork within the project.
5. Integration with development tools: Jira Product Discovery integrates seamlessly with development tools Jira Software, enabling smooth collaboration between product and development teams.
6. Flexibility: Users can customize Jira Product Discovery to fit their specific workflows and processes, providing flexibility to adapt to changing project requirements.


1. Limited service management features: Compared to Jira Service Management, Jira Product Discovery lacks dedicated service management features such as SLA management and incident tracking, which may be essential for customer support teams.
2. Learning curve for non-technical users: While Jira Product Discovery offers a user-friendly interface, non-technical users may still find it challenging to navigate initially, especially if they are unfamiliar with agile methodologies.
3. Pricing: Similar to Jira Service Management, the pricing for Jira Product Discovery can be relatively high, especially for large teams or organizations with specific requirements.
4. Lack of built-in knowledge base: Jira Product Discovery does not include a built-in knowledge base feature like Jira Service Management, which may require teams to use additional tools or platforms for documentation and self-help resources.

AUG Leaders

Atlassian Community Events