JSM Data Center End of Life for Healthcare and Public Sector

17 Nov 2026 · By Ruann van der Merwe, Strategic Advisor — Synapse Software
Strategic Advisor at Synapse Software

For a hospital or a government department, the service desk is rarely just a service desk. It’s where access requests got approved, where security incidents were logged and where someone pasted a patient name or a case number into a ticket because it was the fastest way to get help.

Jira Service Management Data Center goes read-only on March 28, 2029, and Atlassian ends support and security fixes on the same day. The live platform will move somewhere. The question for healthcare and public sector teams is what happens to everything in the old one.

The dates

  • March 30, 2026: new customers can no longer buy Data Center subscriptions or apps. Already passed.
  • March 30, 2028: existing customers can no longer buy new subscriptions, apps or expansions.
  • March 28, 2029, 23:59 PST: subscriptions and apps expire and go read-only. Support and critical security fixes end.

What’s actually in your JSM tickets

Before anyone decides what to keep, look. In healthcare and government, service desk data tends to include:

  • Access requests and approvals for clinical systems or case management systems
  • Security incident tickets and their investigation notes
  • Screenshots and attachments with patient details, case numbers or personal data
  • Change records for systems that handle protected or citizen data

That’s why this data can’t be treated as ordinary IT history. It carries the same sensitivity as the systems it supported.

US healthcare: HIPAA

Two parts of HIPAA matter here.

Documentation retention. HIPAA requires covered entities and business associates to keep documentation of required Security Rule policies, actions and activities for six years. If JSM is where your team logged security incidents, access reviews or risk remediation, some of those tickets may be part of that documentation. Your compliance officer decides which ones.

Risk analysis. Any system holding ePHI belongs in your risk analysis, and risk analysis is still the deficiency OCR cites most often. A JSM instance with no vendor security fixes, still holding patient details in old tickets, is a finding waiting to happen.

HHS has also proposed updating the Security Rule to require a formal technology asset inventory. It isn’t final, and the timeline keeps moving, so treat it as a direction of travel rather than a requirement today.

US public sector: records schedules

Federal agencies follow NARA’s General Records Schedules, and state and local bodies follow their own state schedules. Two details catch teams out.

First, retention doesn’t always run from when a record was created. For some IT records, the retention period starts when the system is superseded or terminated. Retiring JSM can be the event that starts the clock.

Second, most GRS periods are minimums. Agencies can keep records longer if they need them. Either way, someone needs to be able to produce those records for the full period, after JSM is gone.

State and local rules vary, so check your state’s schedule with your records officer.

EU healthcare and public administration: NIS2

NIS2 treats health and public administration as highly critical sectors. Article 21 requires cybersecurity risk management measures, including asset management and access control. Essential entities face fines of up to €10 million or 2% of global turnover.

NIS2 doesn’t name JSM or require any particular archive. But an unsupported system holding sensitive operational data is exactly the kind of risk those measures are meant to cover. Each member state has transposed NIS2 into its own law, so confirm the specifics with your national requirements.

Why read-only JSM isn’t the answer

Leaving JSM running read-only after March 2029 sounds like a cheap archive. In practice you’d be running an unsupported system full of sensitive data, with no security fixes, for as long as your longest retention period. That’s hard to defend in a HIPAA risk analysis or a NIS2 review.

It also has gaps. Atlassian says Assets data can’t be browsed in the interface after the JSM license expires, even though it stays in the database.

What to test before you trust an archive

Use a non-production copy of your own JSM database, since self-service Data Center trials ended in March 2026. Record the archive version you tested, then check:

  • Completeness: the fields, comments, attachments, links and request types in your retention scope are all there.
  • Accuracy: custom fields, cascading selects and Assets references show the same readable values as JSM.
  • Relationships: Assets objects and linked issues come across where a retained record depends on them.
  • Access: clinical, HR or case-related tickets are only visible to the people who should see them, in records, search results and attachments.
  • Performance: long-running tickets with big change histories still open in reasonable time.

Put every gap in the acceptance report with an owner and a decision.

Where Cortex Archive for JSM fits in

Cortex Archive for JSM is self-hosted. It runs in your environment, reads the source database with read-only credentials and doesn’t send your data to Synapse or anyone else. For healthcare and public sector teams, that matters: patient and citizen data stays where your policies already say it should be.

Sign-in runs through SAML or OpenID Connect. Record-level access still needs to be designed and tested for your environment, especially for tickets with patient or case data.

Validate it against your own database, attachments and configuration on the release you plan to run.

Who owns what

  • Compliance or records officer: decides which records are kept, under which rule and for how long.
  • Privacy or security officer: sets who can see sensitive tickets and signs off access testing.
  • Platform owner: owns the JSM exit timeline and the replacement platform.
  • Data lead: extracts, reconciles and reports on the retained data.
  • Business users: confirm they can find and read the records they’ll actually need.
  • Accountable owner: accepts the results and gaps and approves retirement.

Frequently Asked Questions

Do HIPAA retention rules apply to service desk tickets?

Some may. HIPAA requires six years of retention for Security Rule documentation. Tickets that record security incidents, access reviews or risk remediation could fall into that. Your compliance officer should decide which categories count.

Can we keep JSM running read-only as our archive?

You can, but it’s an unsupported system holding sensitive data with no security fixes. That’s a difficult position to defend in a risk analysis or audit.

Does retiring JSM end our records obligations?

No. For some US federal records, retiring the system is what starts the retention period.

Does NIS2 require us to archive JSM data?

NIS2 doesn’t mandate a specific archive. It requires risk management measures, including asset management and access control, which apply to how you handle an unsupported system and its data.

Is the new HIPAA asset inventory rule in force?

No. It’s still a proposed rule as of September 2026. The current Security Rule is what’s enforced.

Where should the archive be hosted?

Wherever your data policies require. A self-hosted archive keeps patient and citizen data inside your own environment.

Retiring JSM Data Center in healthcare or government? Look at Cortex Archive for Jira Service Management and test it against your own records, in your own environment.