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?

[Dang Quang]

Hi @Aditya Mani , 
Thank you for bringing this into production, since Services is becoming more critical part in Incident & Change Management. 

As Compass is being phased out, with DX is replacing it. Does this change enable the sync of DX into Services schema? (currently I can see it can't). 

Another thing, I assume the current attribute types in the Services schema will remain locked down (like add new Tier to Tier attribute), or will the that be open too? 

[Aditya Mani]

Hi @Lior Pinelis - this will have no impact on the "Affected Services" field in Incidents and Changes. The behaviour of this field will remain exactly the same, with some more benefits for the Service object itself like ability to add custom attributes, ability to add permissions to the service objects.

[Aditya Mani]

Hi @Rune Rasmussen - This will have no impact on how change and incident management features will behave. From a rollout standpoint, currently this new feature will only be visible to new customers and signups in to Service Collection. We will be rolling out these changes to existing customers in the next couple of months, and we will make another announcement for it.

[Aditya Mani]

Hi @Daniel Johnson - That is correct. We will support import via CSV and JSON and the other import channels already present in Assets.

[Lior Pinelis]

@Aditya Mani when you say no impact, will it continue to be a Compass service lookup, or will it be updated to utilize the new Assets?

How is the migration going to look like from Compass Components into the new Service Assets?

[Aditya Mani]

Hi @Peter Miklian - At the moment, the services are excluded from the Assets limit.

[Aditya Mani]

Hi @Dang Quang -

• Unfortunately, we will not be enabling a sync between DX and the Services schema
• In the new Services schema, the attribute types for the default attributes will be locked. So, you will not be able to add a new "Tier 5" in your example. But you should be able to create new custom attributes and assign new values to them

[Lior Pinelis]

@Aditya Mani is it possible to have this feature enabled only in Sandbox for existing customers to test and plan on the migration in prod?

[Quang Kieu]

Thank you @Aditya Mani 

Will there be alternative solution for sync into Services schema (since this was possible in the past with Compass)? 

[Aditya Mani]

Hi @Lior Pinelis - 

• About the Compass sync - if you have Compass components synced with a JSM service, that sync will continue as is. Which means now the Services present in Assets will be synced with the Compass components. Further, any JSM service that could be added as an "Affected Service" to an Incident/Change will continue in the same way after the migration also
• About sandbox - we will not be able to enable this in sandbox for you. But once the migration begins, you will have a few months of transition period where both sets of schemas will co-exist for you to be comfortable with the change. We will share some more details on this in a few weeks

[Aditya Mani]

Hi @Quang Kieu - Not at the moment. DX and JSM will remain in an un-synced state.

[Saki Okubo]

@Aditya Mani 

Will this update allow us to specify “Affected Services” in the context settings for asset object fields?

[David Washburn]

Is there an EAP we can register for this? We're in the process of overhauling our incident management / services workflow and custom fields on services would be a game changer.

Also will there be an automated way to generate services from Datadog, or similar tools?

[Aditya Mani]

Hi @Saki Okubo - If I am not mistaken, the screenshot you have shared is the screen that shows up in the configuration of a Jira work item Assets custom field. In this screen and setting, you should be able to reference the Services objects after the update. However, the "affected services" field continues to remain a separate field, and that will continue referencing the Services objects only, not other objects from Assets.

[Aaron Koenig]

Just wanted to confirm any paid license that includes JSM will continue to be able to utilise the Services. e.g. Premium Jira Service Management.

[Aditya Mani]

Hi @David Washburn - To answer your first question, we do not have an EAP for this release. If you are an existing customer of JSM, then you will fall in the migration cohort, the details of which we will share with the community shortly. The timelines for migration will be around July. 

Also, about automatic discovery of services from Datadog - this is a roadmap item for us and will be available soon.

[Aditya Mani]

Hi @Aaron Koenig - That understanding is correct. Any paid license of JSM will continue having access to Services. This includes Standard, Premium and Enterprise.

[Gerrit Wahlers]

Hi, is there any way to sync jira groups that are coming from atlassian guard to stakeholder groups, asset groups (employees), organizations and jira teams? Or do we have to setup all manually?

We use Jira ITSM internally.