How services work across Jira Service Management and Compass
Who this is for: Anyone using both Jira Service Management and Compass who wants to understand what data flows between the two products. There's no setup task — the sync is automatic.
Services aren't available on the Free plan after 31 July 2026. Upgrading to any of our paid plans (Standard, Premium or Enterprise) will unlock access to Services.
When eligible Jira Service Management and Compass sites are connected, supported services and components are kept in sync across the two products.
Services in Jira Service Management live in two pre-provisioned Assets schemas — Software Registry and Business Portfolio. Objects in both schemas appear as Compass components when the products are connected.
This means you don't maintain two separate catalogs. Update a service in Jira Service Management and Compass sees the change; create a component in Compass and Jira Service Management sees it as a service.
When does the sync happen?
This feature is only available to customers who gained access to both Compass and Jira Service Management after January 2024.
The sync is automatic once both products are active on your Atlassian organization. There's no button to press, no integration to configure, and no per-service setup. Services and components are two product views of the same record.
In order for the data to sync automatically, the created service must be one of the following:
ソフトウェア サービス
機能
アプリケーション
What syncs between Jira Service Management and Compass
The following fields are kept in sync automatically:
フィールド | How it syncs |
|---|---|
名前 | Two-way |
説明 | Two-way |
Tier階層 | Two-way |
Service object type → component type | If the service or component is created from a Software Services, Capabilities, or Applications type service then a corresponding entity is created in the other product. If someone changes the component type in Compass, sync with the Jira Service Management service can break. |
Permissions are not shared between the two products. Each product enforces its own permissions independently. Edit access in Jira Service Management doesn't grant edit access in Compass for the same service, and vice versa.
What you get in Compass for a synced service
Once a service is visible in both products, Compass picks up the following for engineering teams:
Incidents appear on the Compass component view. When a service is added to an incident's Affected services field in Jira Service Management, the incident shows up against the matching Compass component — so engineering teams see live operational state without leaving Compass.
For more on incidents, see How services work with alerts and incidents.
What happens if a service is removed from Jira Service Management
If a Jira Service Management service is deleted, the matching Compass component is not deleted — it remains in Compass as a standalone component. You can manage or delete it from Compass independently.
トラブルシューティング
Issue | What to do |
|---|---|
My Jira Service Management services aren't showing up in Compass. | Confirm that both Jira Service Management and Compass are active on the same Atlassian organization. The sync depends on the org-level connection — without both products active, services and components stay separate. Also confirm that access was gained to both Compass and Jira Service Management after January, 2024. |
I updated a service in Jira Service Management but the change isn't visible in Compass yet. | Sync usually completes within a few minutes. If the change hasn't appeared after 10 minutes, refresh Compass. If the problem persists, contact Atlassian Support. |
I can edit a service in Jira Service Management but not the matching component in Compass. | Permissions are enforced independently by each product. You need edit permission in Compass to edit the component there — even if you can edit the same service in Jira Service Management. |
この内容はお役に立ちましたか?