Unifying Services, Assets and Jira Service Management

[#1]

Today we’re sharing an important update to unify our Service from Compass with Assets and Jira Service Management. Now you’ll be able to connect those requests to the real-world things behind them devices, software, users, vendors, and the services they support. Agents can triage faster, resolve incidents with more confidence, and prevent repeat issues.

What this unlocks for you

Beyond unifying your service data into one place, this removes several long-standing limitations of the existing Jira Service Management services. Here's what's new:

Control who can do what with granular permissions

With the new enhancements, services are Assets objects, which means you can assign permissions to service objects the same way you already do for any other Assets object. Define who can view, edit, or manage individual services and tailor access to match your organizational structure and compliance needs.

Extend your service model with custom attributes

The old services schema was locked. You couldn't add your own fields or adapt the data model to fit how your organization actually thinks about services. That changes now. With the new services experience, you can add custom attributes to services. Just like you do for any other Assets object type. Whether you need to track cost centers, SLA tiers, compliance classifications, or business owners, you can shape your service catalog to reflect what matters to your team.

Create and edit services directly in Assets

With this launch, you can create and edit service objects directly in Assets, just like any other object. This gives you a single, consistent interface for managing your entire configuration management database, including your services, without switching between tools.

We’re unifying the Services with Assets: to give every team a single, trusted view of services and the real-world things behind them. With full, shared visibility across departments and teams, you can triage faster, resolve with more confidence, reduce repeat outages, and improve reliability and SLAs.

When is this happening?

If you’re on Jira Service Management / Service Collection Free

• What’s changing:

  • Free Jira Service Management and Service Collection customers who use Services today will lose access to their Services after July 31, 2026, unless they upgrade to a paid plan.

  • From April 21, 2026 we will no longer enable new free customers to access Services.

• What you should do:

  • If the Services is important to your workflows, plan an upgrade to a paid plan before July 31, 2026 to merge your objects into Assets.

• Will I be charged for Services objects now that they are moving under Assets?

  • We’re moving Services into Assets to give you a single, more powerful place to manage and relate services with your teams, incidents, and CMDB data. At this time, This change won’t result in any charges right now.

• Is there a migration process?

  • Yes, for paid plans we will have a migration process with more details coming soon.

[Lior Pinelis]

@Aditya Mani how is this going to impact "Affected services" field on the Incident tickets. This native field is a lookup to a Compass Components services records.

[Rune Rasmussen]

This will fix some of the main shortcomings of Services that has been blocking us from working with it.

Will this also have an impact on how Incident or Change management features behave?

And what does the rollout plan/schedule look like?

[Daniel Johnson]

With being able to "create and edit service objects directly in Assets, just like any other object," does this mean we will be able to use bulk imports (CSV, JSON, etc.)?

[Peter Miklian]

Will Services, like other assets, be counted toward the asset limit, or are they excluded from it?