Jira Service Management Review: IT Ticketing and Project Tracking

The research in brief

Jira Service Management is a good fit for IT managers who need help desk ticketing and planned IT project work connected in one system, especially when the organization already uses Atlassian products. Five of six platforms named it during the ranking stage, with an average listed rank of 1.6 and a best rank of 1. Its strongest advantage is native integration between service tickets and Jira Software project work, plus configurable SLAs, escalation automation, and Premium-tier asset and change management. The main limitation is that integration spans two separately licensed Atlassian products, and advanced ITSM features sit behind the more expensive Premium tier.

Research Snapshot

Why Jira Service Management Qualified for This Study

Questions explored

• Why did Jira Service Management qualify for a study on IT ticketing and project tracking integration?
• How many AI platforms recommended Jira Service Management for unified help desk and IT project work?

Jira Service Management qualified because it was named by five of the six included platforms during the ranking stage, giving it an 83.3% share of included platform responses and an average listed rank of 1.6 ^[30]. It ranked first on Claude, DeepSeek, and ChatGPT, third on Grok, and second on Perplexity.

The study's research prompt asked which providers could handle day-to-day help desk tickets alongside larger IT projects such as system migrations or rollouts, with SLA tracking, escalation rules, and reporting that separates routine support work from planned initiatives. Jira Service Management was repeatedly recommended for exactly that combination because Jira Service Management and Jira Software are distinct Atlassian products on a shared platform that can be linked so service requests and software project issues are tracked together ^[14].

Platforms also cited documented SLA, automation, change, and asset management capabilities aimed at IT service teams ^[26]. The entity's official website is, and the relevant deployment for this use case is Jira Service Management Cloud Premium combined with Jira Cloud Premium ^[30].

The software offering in focus

Questions explored

• Which Jira Service Management plan should a buyer choose for IT ticketing and project tracking integration?
• Is Jira Service Management Premium required to connect help desk tickets with Jira Software project work?

The most relevant configuration is Jira Service Management Cloud Premium combined with Jira Cloud Premium, using native Jira Software integration ^[30]. Platforms converged on Premium rather than Standard because advanced incident, problem, change, asset, and AIOps capabilities moved into Premium and Enterprise tiers ^[19].

Jira Service Management uses Jira work items and can connect service-management services with Jira Software, allowing operational incidents and related information to appear in Jira Software ^[16]. Atlassian documents linking JSM requests to Jira Software issues so service work and engineering project work can be tracked together ^[14]. Independent reviews describe bidirectional behavior: customer-reported incidents automatically create development tickets, developer updates sync back to the service desk in real time, and the service desk ticket closes automatically with resolution notes when the fix deploys ^[40].

One unresolved question is whether Jira Software Premium is strictly required for bidirectional integration or whether Standard Jira Software can support ticket-to-project linking; the documentation references integration capability but does not explicitly state a plan-level dependency. Buyers should confirm this before budgeting.

What the AI Platforms Agreed About

Questions explored

• What do AI platforms agree Jira Service Management does well for IT ticketing and project tracking integration?
• Does Jira Service Management provide SLA tracking and escalation automation for IT help desks?

Platforms agreed unanimously on several points. All six described native or documented integration between Jira Service Management and Jira Software as the core reason to consider the product for this use case ^[16].

They also agreed on SLA and escalation capability. Jira Service Management supports configurable SLAs with multiple goals and conditions, and SLA behavior depends on configuration - changing start or stop conditions can close, restart, or remove open SLA cycles ^[12]. Independent reviews describe automated escalation rules that prevent SLA breaches, with escalations triggering when response or resolution targets are at risk ^[51].

A third area of agreement was asset and change tracking on Premium. Cloud Premium includes Assets, advanced incident and change-management capabilities, deployment tracking, and CI/CD change gating ^[30]. Atlassian lists 50,000 included Assets objects for Service Collection Premium, with additional consumption potentially chargeable ^[19].

Platforms also agreed that Premium includes a financially backed 99.90% uptime SLA and 24/7 premium support with one-hour response times for critical issues, subject to Atlassian's SLA terms and service-credit process ^[18].

Where the AI Platforms Disagreed or Were Uncertain

Questions explored

• What are the biggest uncertainties about Jira Service Management reporting on tickets versus projects?
• Do AI platforms disagree about Jira Service Management pricing and plan packaging?

Reporting on tickets versus projects was the clearest area of uncertainty. OpenAI found that Jira provides a shared work-item and project data model that can support cross-functional reporting, dashboards, queues, and traceability, but the checked sources do not establish that a single out-of-the-box report automatically compares ticket workload against planned project delivery ^[30]. Anthropic went further, reporting that project-scoped analytics prevent unified reporting across IT teams and departments, with no native capability to track SLA breaches by business unit ^[42]. Perplexity noted that Atlassian states change reports are included and Assets reporting can cover objects, related issues, and projects, but direct out-of-the-box reporting that cleanly separates ticket metrics from project metrics is not fully clear from the sources checked ^[30].

Pricing was the second disagreement. Anthropic reported Premium at $51.42 per agent per month on annual billing, roughly $53.30 on monthly billing, and about $514 per month or $6,170 per year for a 10-agent team ^[48]. Grok reported approximately $47.82 per agent per month annual for JSM Premium plus approximately $14.54 per user per month annual for Jira Software Premium ^[47]. Kimi reported roughly $47 per agent per month annual for Premium and $19 for Standard. Perplexity listed Service Collection pricing at $51.42 per agent per month and Jira Cloud Premium at $14.54 per user per month ^[21]. One source cited by Claude listed Premium at $40 per agent per month, which conflicts with all other sources and was classified as unreliable.

Packaging was also unresolved. Atlassian's current materials refer both to Jira Service Management Cloud Premium and to Service Collection packaging, and the exact 2026 commercial bundle for a new United States purchase should be verified. Whether Jira Service Management is sold standalone or only through Service Collection packaging is an open question.

Features for this workload

Questions explored

• Does Jira Service Management support workflow automation and escalation rules for IT processes?
• Can Jira Service Management link assets and change requests to help desk tickets?

Ticket and project integration is the strongest documented advantage. Jira Service Management uses Jira work items and can connect service-management services with Jira Software, allowing operational incidents and related information to appear in Jira Software ^[16]. The integration is native within Atlassian Cloud, but project planning and service management may still involve separate products, projects, permissions, and subscription entitlements ^[16].

SLA and escalation tracking is configurable. Jira Service Management supports configurable SLAs with multiple goals and conditions, and SLA behavior depends on configuration ^[12]. Independent reviews describe automated escalation rules that prevent SLA breaches, with escalations triggering when response or resolution targets are at risk ^[51]. Cross-project escalations between JSM and Jira are documented, with incidents logged by customers instantly linked to engineering bugs and SLA timers reflecting the real-time status of the linked engineering task ^[46].

Workflow automation for IT processes is a Premium advantage. Cloud Premium includes global automation across products and projects, with 6,500 global automation steps listed in the plan comparison ^[30]. Premium also includes change-management automation and deployment gating capabilities ^[30]. Anthropic reported 1,000 rule runs per user per month on Premium.

Asset and change tracking is Premium-gated. Cloud Premium includes Assets, advanced incident and change-management capabilities, deployment tracking, and CI/CD change gating ^[30]. Assets provides a centralized repository linking hardware, software, and licenses to service requests, incidents, problems, and changes ^[37]. Change management connects change requests to development and operations workflows with automated risk assessment, multi-stage approvals, and CI/CD integrations ^[20].

Reporting on tickets versus projects is the weakest area. Jira provides a shared work-item and project data model that can support cross-functional reporting, dashboards, queues, and traceability, but the checked sources do not establish that a single out-of-the-box report automatically compares ticket workload against planned project delivery ^[30]. Anthropic reported that project-scoped analytics prevent unified reporting across IT teams and departments ^[42].

Pricing, renewal terms, and ongoing costs

Questions explored

• How much does Jira Service Management Premium cost per agent per month in 2026?
• What additional fees should a buyer expect beyond the Jira Service Management subscription?

Exact 2026 pricing was not established from the checked sources, and platform-reported figures conflict. Atlassian prices Cloud products per user using progressive monthly pricing or annual user tiers; current pricing depends on user counts, product or collection packaging, edition, and possible add-ons ^[22]. The relevant deployment is likely Jira Service Management Cloud Premium plus Jira Cloud Premium, unless Atlassian's current Service Collection packaging supplies the required combination.

Platform-reported figures include $51.42 per agent per month annual for Premium ^[48], approximately $47.82 per agent per month annual ^[41], and roughly $47 per agent per month annual. Jira Software Premium was reported at approximately $14.54 per user per month annual ^[47]. Standard was reported at $20 per agent per month ^[43] and roughly $19 per agent per month annual. These figures are platform-reported and were not verified from a live pricing calculator.

Additional fees to verify include Assets usage above the included allowance, which Atlassian's published packaging update states starts at $0.05 per object per month above 50,000 objects, subject to volume discounts ^[19]. Grok reported a different overage figure of $0.02 per object per month. Virtual Service Agent assisted conversations may have consumption-based charges above included usage, with Perplexity reporting $0.30 per conversation per month with volume discounts ^[30]. Atlassian Guard may be required for SSO, SCIM, or directory synchronization on Standard and Premium plans. Third-party Marketplace apps and their support or licensing fees are separate ^[8].

Contract terms: monthly Cloud subscriptions are billed based on active users and progressive per-user pricing, while annual subscriptions use user tiers that Atlassian states cannot be altered or changed during the annual term ^[22]. Premium trials are available, but trial duration differs for new versus existing customers and for monthly versus annual subscriptions. Perplexity reported a 7-day trial for new customers and a fixed 30-day trial for annual subscriptions ^[30]. Premium SLA compensation is provided as service credits subject to Atlassian's SLA request conditions ^[18].

Best Suited For

Questions explored

• Is Jira Service Management a good choice for IT teams already using Jira Software and Confluence?
• Which IT organizations get the most value from Jira Service Management Premium?

Jira Service Management is best suited for IT teams already using Jira Software, Confluence, Bitbucket, or other Atlassian products. Organizations needing ITIL-oriented incident, change, problem, SLA, asset, and deployment workflows alongside planned project work are a strong fit. Teams requiring customizable workflows, automation, reporting, and traceability between operational tickets and engineering or infrastructure projects also fit well.

Anthropic added that mid-to-large IT operations needing ITIL-aligned workflows with incident, change, and asset management are well matched, as are environments where incident resolution requires developer involvement or tracking deployment progress. Deepseek noted buyers who want one vendor for ITSM ticketing plus agile project tracking without building custom middleware integration are a good fit.

Probably Not Best Suited For

Questions explored

• Who should not choose Jira Service Management for IT ticketing and project tracking integration?
• Is Jira Service Management too complex for small IT teams with limited administration resources?

Small teams wanting the simplest help desk and lightweight project tracker with minimal administration should look elsewhere. Buyers seeking one bundled subscription and predictable pricing without separate Jira, Service Collection, Marketplace, or security add-on costs are also a weaker fit.

Anthropic reported that non-technical service managers who require minimal configuration complexity, organizations needing full ITSM capabilities without moving from Standard to Premium, and teams with strict on-premise or hybrid deployment requirements are not well suited. Multiple independent sources document that Jira Service Management requires significant setup complexity, steep learning curves, and technical expertise, with non-technical teams reporting difficulty with workflow customization and often weeks or months of configuration ^[42].

Customer reviews consistently document UI complexity, cluttered interface design, and excessive clicks required for simple tasks, with the platform described as difficult for non-technical users ^[44]. Knowledge management requires manual creation and maintenance of articles without automatic gap detection or generation from resolved tickets ^[42]. Multi-channel support is limited: Jira Service Management connects to only one Slack workspace per Jira site, lacks built-in phone support, and offers limited omnichannel routing ^[42].

When Another Option May Be Better

Questions explored

• What is a better alternative to Jira Service Management for a buyer who needs one bundled ITSM and project license?
• When should a buyer choose ServiceNow or ManageEngine instead of Jira Service Management?

OpenAI recommended considering a simpler help-desk or project platform when the team has basic ticketing needs, few workflow variations, and does not need deep Jira engineering integration. ServiceNow may be better when the buyer needs a broader enterprise ITSM operating model, extensive CMDB and governance depth, or a highly standardized large-enterprise implementation, accepting higher complexity and cost. ManageEngine or similar ITSM suites may be better when bundled endpoint, asset, and service-desk capabilities matter more than Jira-native software-development integration.

Anthropic recommended alternatives when the buyer requires lightweight, plug-and-play ticketing without significant configuration or technical expertise, lacks Atlassian infrastructure, needs unified cross-department reporting or advanced omnichannel support out of the box, or has a constrained budget and needs full ITSM capabilities without accepting the 2.5x cost multiplier from Standard to Premium. Deepseek noted that a single all-in-one license and a single admin surface for both ITSM and project tracking may point to a different product.

Kimi recommended alternatives when budget favors all-in-one tools like Freshservice or Linear with lower total cost of ownership, when the primary need is simple ticketing without software development coordination, or when cross-company sync with ServiceNow, Salesforce, or Zendesk is central. Perplexity noted that a buyer wanting a simpler, lower-admin help desk with minimal project management, or a single bundled ITSM/project suite with less reliance on multiple Atlassian products, may be better served elsewhere.

Questions to ask before choosing a provider

Questions explored

• What should a buyer confirm with Atlassian before signing a Jira Service Management contract?
• How should a buyer verify Jira Service Management total cost before purchase?

Buyers should confirm whether Jira Service Management is sold standalone for this purchase or only through the current Service Collection packaging. They should also confirm whether the selected entitlement includes Jira Software Premium or whether Jira Cloud Premium must be purchased separately.

Other verification items include which users require agent, requester, developer, project, or administrative access and how those users are billed; whether required ticket-to-project links, cross-project boards, dependencies, dashboards, and reports are available natively or depend on Marketplace apps; which SLA calendars, pause conditions, escalation paths, and reporting metrics are supported without custom development; and what the included Assets object allowance, virtual-agent allowance, and current overage prices are for the proposed edition.

Buyers should also verify whether Atlassian Guard, Marketplace integrations, implementation services, or data migration services are required; whether Cloud, Data Center, or a hybrid architecture is needed and whether required integrations and controls are available in that deployment; what data residency, retention, audit, identity, and integration-data-sharing requirements apply; and what happens to open SLA cycles, reports, workflows, and integrations if the organization downgrades, cancels, or changes plans.

Anthropic added questions about in-house technical resources for workflow configuration, required time-to-value, incident-to-deployment tracking needs, reporting requirements beyond ticket SLA and closure metrics, on-premise infrastructure requirements, knowledge management strategy, and willingness to accept single Slack workspace integration and no native phone support.

The consensus assessment

Jira Service Management Cloud Premium with Jira Cloud Premium is a strong fit for IT managers who want one Atlassian-centered operating environment connecting help-desk tickets with planned IT and engineering project work. It is strongest when the organization values Jira-native integration, configurable ITSM workflows, SLA tracking, change and asset management, and extensibility.

Fit ratings split between strong (ChatGPT, Grok, Kimi) and good (Claude, DeepSeek, Perplexity). Anthropic rated it good rather than strong due to the significant cost multiplier required to unlock core ITSM features in Premium, implementation complexity and steep learning curves, limitations in cross-team reporting, and usability challenges documented in multiple independent reviews. Deepseek rated it good, noting that integration is cross-product rather than single-product, licensing usually means two subscription lines, some capabilities are tier-gated, and cross-product reporting commonly needs additional tooling.

It is a weaker choice when simplicity, bundled pricing, minimal administration, or highly prescriptive enterprise ITSM governance matters more than Jira ecosystem integration. Buyers should verify exact 2026 pricing, plan packaging, and reporting capabilities before purchase, because platform-reported figures conflict and the checked sources do not establish a single out-of-the-box report comparing ticket workload against planned project delivery ^[42].

How This Review Was Produced

This review synthesizes fit-research responses from six AI platforms: Claude (claude-haiku-4-5-20251001), DeepSeek (deepseek-v4-flash), Grok (x-ai/grok-4.3), Kimi (moonshotai/kimi-k2.6), ChatGPT (gpt-5.6-luna), and Perplexity (perplexity/sonar). Each platform was asked which providers would be recommended for an internal IT manager who wants a single system handling day-to-day help desk tickets alongside larger IT projects like system migrations or rollouts, with SLA tracking, escalation rules, and clear reporting distinguishing routine support work from planned initiatives.

Five of six platforms named Jira Service Management during the ranking stage. The research date is 2026-10-02. Platform-reported research dates differ: DeepSeek reported 2026-01-15 while the other five platforms reported 2026-10-02. These platform-reported dates are provenance metadata and do not independently prove freshness.

All included platforms evaluated fit, but platform_mentions counts only platforms that named the entity during ranking discovery. The supplied URLs were collected from platform responses and were not independently validated by the writer stage. Company-owned citations materially outnumber independent citations, and company claims should not be described as independently verified. Citations are platform-reported evidence, not independently verified facts. No-search model claims require explicit verification before being described as current facts.

Research limitations

This review has several limitations. First, exact 2026 list prices, user-tier calculations, included virtual-agent usage, and Assets overage rates were not fully verified from a live pricing calculator. Platform-reported pricing figures conflict, ranging from $47.82 to $53.30 per agent per month for Premium depending on volume tier and billing cycle.

Second, the sources reviewed establish integration and ITSM capabilities but do not independently validate implementation effort, customer outcomes, or total cost of ownership. Third, whether Jira Software Premium is strictly required for bidirectional integration or whether Standard Jira Software can support ticket-to-project linking is unclear from the documentation.

Fourth, asset management feature availability may differ between Service Collection Premium and JSM-only Premium tiers, and documentation uses both naming conventions without clear delineation. Fifth, official-site retrieval failed for the entity's homepage, and the matching reported domain was retained for downstream research but remains unverified (normalization_notes). Sixth, platform-reported research dates differ from the authoritative run date, and DeepSeek's research date of 2026-01-15 is more than eight months older than the run date.

Seventh, the deterministic identity audit contains qualification notes that should be disclosed: official-site retrieval failed for one or more mentions, identity used exact-name fallback, and company-name variants were collapsed onto one canonical brand before minimum_mentions qualification (normalization_notes). Eighth, the fit ratings are platform opinions based on the evidence each platform retrieved, and AI-platform agreement does not prove product quality.

See the broader IT Teams Needing Integrated Ticketing and Project Tracking consensus index for comparisons across qualified options.

Explore more project management and team collaboration software guidance in the category directory.

Sources

Company-Owned Sources

1. 10 Jira Service Management Automation Rules That Every Team Should Use: https://community.atlassian.com/forums/App-Central-articles/10-Jira-Service-Management-Automation-Rules-That-Every-Team/ba-p/3220196
2. Managing changes with your IT service project: https://confluence.atlassian.com/servicemanagementserver/managing-changes-with-your-it-service-project-939926632.html
3. Project management automation: SAP – Jira integration overview – Celigo Help Center: https://docs.celigo.com/hc/en-us/articles/36719638441371-Project-management-automation-SAP-Jira-integration-overview
4. Siit Documentation: Ticketing Integrations: https://docs.siit.io/integrations/ticketing
5. Exalate Review: A Technical Evaluator's Guide to What It Does: https://exalate.com/blog/exalate-review/
6. Bidirectional Real-time Jira Service Management Integration - Exalate: https://exalate.com/integrations/jira-service-management/
7. How to use Jira Cloud sync | Asana Help Center: https://help.asana.com/s/article/asana-for-jira-cloud?language=en_US
8. Atlassian Marketplace: https://marketplace.atlassian.com/
9. What’s in Assets for Cloud?: https://support.atlassian.com/assets/docs/what-are-the-differences-between-assets-in-cloud-and-server/
10. Explore Jira Cloud plans - Atlassian Support: https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/
11. Add a global integration: https://support.atlassian.com/jira-service-management-cloud/docs/add-an-integration-site-level/
12. Create and edit an SLA: https://support.atlassian.com/jira-service-management-cloud/docs/create-an-sla/
13. Get to know the main Jira Service Management features: https://support.atlassian.com/jira-service-management-cloud/docs/get-to-know-the-main-jira-service-management-features/
14. Atlassian Documentation – Integrate Jira Service Management with Jira Software: https://support.atlassian.com/jira-service-management-cloud/docs/integrate-jira-service-management-with-jira-software/
15. Integrations - Atlassian Support: https://support.atlassian.com/jira-service-management-cloud/docs/integrations/
16. Connect Jira Service Management services to Jira Software: https://support.atlassian.com/jira-software-cloud/docs/connect-jira-service-management-services-to-jira-software/
17. Supported Atlassian apps and types of links: https://support.atlassian.com/migration/docs/supported-products-and-types-of-links/
18. Service Level Agreement for Atlassian cloud apps: https://support.atlassian.com/subscriptions-and-billing/docs/service-level-agreement-for-atlassian-cloud-products/
19. Jira Service Management pricing and packaging updates: https://www.atlassian.com/blog/jira-service-management/jsm-cloud-pricing-packaging-update
20. IT Service Management (ITSM) Guide: https://www.atlassian.com/collections/service/guides/it-service-management
21. Service Collection Pricing: Free and Paid Plans - Atlassian: https://www.atlassian.com/collections/service/pricing
22. Atlassian Cloud Licensing: https://www.atlassian.com/licensing/cloud
23. Compare Jira Service Management Cloud and Data Center features: https://www.atlassian.com/migration/assess/compare-cloud-data-center/jira-service-management
24. Pricing: https://www.atlassian.com/software/jira/pricing
25. Atlassian Cloud Plans and Pricing: https://www.atlassian.com/software/jira/service-management
26. Jira Service Management Features: https://www.atlassian.com/software/jira/service-management/features
27. Bring Complete, Current, And: https://www.atlassian.com/software/jira/service-management/features/asset-and-configuration-management
28. ITSM Software Features | Atlassian: https://www.atlassian.com/software/jira/service-management/features/itsm
29. Jira Service Management & Jira Software Integration | Atlassian: https://www.atlassian.com/software/jira/service-management/jira-integration
30. Jira Service Management Cloud Premium: https://www.atlassian.com/software/jira/service-management/premium
31. Atlassian Pricing: https://www.atlassian.com/software/jira/service-management/pricing
32. Integrate Jira Service Management with Jira: https://www.atlassian.com/software/jira/service-management/product-guide/tips-and-tricks/jira-service-management-and-jira
33. Assets for Jira Service Management Data Center - Atlassian: https://www.atlassian.com/software/jira/service-management/resources/insight-data-center-get-started-guide
34. JSM-ServiceNow Integration | Two-Way Sync | Getint: https://www.getint.io/integrations/jira-service-management-servicenow
35. Jira-Zendesk Integration | Two-Way Sync | Getint: https://www.getint.io/integrations/jira-zendesk
36. Atlassian and HubSpot integration: real-time two-way sync - StackSync: https://www.stacksync.com/integrations/atlassian-and-hubspot

Independent Sources

37. Jira Asset Management for IT Infrastructure: https://appsvio.com/blog/jira-asset-management/
38. Jira Service Management - AWS Marketplace Reviews: https://aws.amazon.com/marketplace/reviews/reviews-list/prodview-mlqqwfixthul4?page=26
39. Jira Service Management Ticketing System: All You Need To Know in 2026: https://clearfeed.ai/blogs/jira-service-management-ticketing-system-guide
40. Jira Service Management Integration With Jira Software 2026: https://exalate.com/blog/jira-service-management-integration/
41. Jira Service Management Pricing: Detailed Breakdown (2026: https://ones.com/blog/jira-service-management-pricing-detailed-breakdown/
42. Jira Service Management Limitations: What Jira Service Management Cannot Do: https://unthread.io/blog/jira-service-management-limitations/
43. Jira Service Management Pricing 2026: Real Costs: https://unthread.io/blog/jira-service-management-pricing/
44. Best Jira alternatives for IT and customer support teams: https://www.deskpro.com/blog/jira-alternatives-it-customer-support
45. Jira Service Management Reviews 2026: Details, Pricing, & Features: https://www.g2.com/products/jira-service-management/reviews
46. Advanced Jira Automation Rules for Complex Workflows in JSM: https://www.getint.io/blog/advanced-jira-automation-rules
47. Jira Pricing in 2026: Every Plan, Every Tier, Every Cost | JiraCost.com: https://www.jiracost.com/pricing/
48. Jira Service Management Pricing 2026: Plans & Costs: https://www.motadata.com/blog/jira-service-management-pricing
49. Jira Service Desk Expert Review, Pricing, Alternatives - 2026: https://www.selectsoftwarereviews.com/reviews/jira-service-desk
50. Jira Service Management Review: Is It Worth it in 2026?: https://www.smartsuite.com/blog/jira-service-management-review
51. Jira Service Management: Features, benefits & best practices: https://www.tempo.io/blog/jira-service-management
52. Jira Service Management pricing under the Service Collection: https://www.togetha.group/blog/jira-service-management-pricing