--- title: "Atlassian Compass Integration" canonical: "https://help.releasemanagement.app/space/RMC/2506129435/Atlassian%20Compass%20Integration" format: markdown --- > Macro (include) > 📝 As Atlassian has [officially](https://support.atlassian.com/compass/docs/migrate-from-compass-to-dx/) decommissioned Compass and is transitioning its core capabilities (software component tracking, scorecards, and catalog management) to DX (DX Fabric), we are refocusing on our own [cross-component management capabilities](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/2599616526) and component release model. > 📝 > 📝 This includes the ability to create relationships between space-specific components and releases, as well as between cross-space components and releases. In the near future, we also plan to introduce dependency management and tracking capabilities. > 📝 > 📝 As a result, the [Compass App](https://marketplace.atlassian.com/apps/1238099/release-management-integration-for-compass?hosting=cloud&tab=overview) will be retired at the appropriate time, and all Compass-related functionality within Release Management will be replaced by our cross-space component framework. > 📝 > 📝 These capabilities will be introduced as part of Release 1.0 of our Runs on Atlassian (ROA) app for new customers by the end of Summer 2026, with migration of existing customers planned through the end of 2026. > 📝 > 📝 Stay tuned! # Topics > Macro (toc) # What is Atlassian Compass? Compass is a [mission control for your distributed architecture](https://www.atlassian.com/software/compass), namely - proper artifactory natively integrated into Jira - proper implementation of Component field for Jira issue (though it’s called CompassComponent) - proper scoring of your entire architecture landscape healthiness # Why we decided to integrate Release Management with Atlassian Compass? For a long time we are considering how to connect a notion of version/package we have in Release Management App with a notion of product being released. Once of the mostly used use case for the App is using versions to track releases of specific components (Services, Microservices, Databases, ETLs, Web, Mobile Apps, etc.) and package them into release that goes cross components and either needs to be delivered together or could be turned on with feature flag when all the components are upgraded. From this perspective integration with Compass for us is either a silver bullet or something very close to it as it gives Release Management users: - Connect releases with software components (artifactory items) - Understand dependency between components and thus propagate this dependency to release management - Understand health check (scoring) of components as a quality gateways prior to release - Introduce a notion of the team owning the component and therefore act as enginning arm behind the release (if not owning the release as well) - etc. # Compass tab on Release details Starting from the late Feb’23 release of the App you can now enjoy the integration with Compass. To check it out click on any version or release. You will see a new “**Compass**“ tab available between “**Issues**“ and “**Commits**“. ![image](media://d5577b7d-1780-40e9-bbcc-4672f7ce965d) > 📝 As of **April, 2026** we are rolling out a cross-product App thus removing the need to use API tokens for Compass integration. Same time you have to connect Compass in Jira Admin to our App so you can use **Compass Integration** functionality. So, there rest of this section (with regards to using API tokens for access) might become obsolete shortly if not already. > 📝 > 📝 [https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/3934257153](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/3934257153) If you are using Release Management integration with Git, Bitbucket and CI/CD tools there’s no need to configure the shake hand with Compass - we will re-use your generated token. If you are new to these integrations or had no chance to configure Release Management integration with Git, Bitbucket and CI/CD tools yet please check out this [section to generate API token](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/1004601345/Git+Bitbucket+CI+CD+tools+Integrations#Getting-started). ## Compass Components Once configured you can click up on look up of Compass Components to assign specific components to your release. ![image](media://687b8ced-5654-4106-9291-569286469cf0) ![image](media://5128a927-20d9-4aa1-ad4d-1c7273371480) From Compass we will pull - **Name **of the Components and Compass specific icon of this component/type. By clicking on the name you will navigate to Compass to gain more details. - **Description **of the Components - **Tier **of the Components in the hierarchy - **Team **the owns the Component. By clicking you will be navigated to the Compass space of the team. - **Scorecard** of the component to outline health check details. To remove Release <> Component binding click on the “**X**“ button on the right. ### **Impacted components** In addition to Components you assigned manually we will check all the issues assigned to the release and outline all Compass Components defined for issue giving you an indication that those “probably“ should be included in the list. ## Component Dependencies If you have some Compass Components defined on the “Components“ tab, switching to “Dependencies“ tab will lead you to other “Depends on“ and “Depended by“ Compass Components. ![image](media://0e845a35-baf6-453e-953c-a08f58f108bd) ![image](media://03f25d4e-ce57-4dcd-80eb-b8c168770a10) This is a good indicator to check what other Component Releases might be impacted by the change. Or if existing component release might be impacted by any other dependency. ## *Coming soon* We are working at the moment onto Teams sections of integration. Shortly after we will also deliver a functionality to filter by Compass Components, Teams on Board, Roadmap, Calendar and List views. Also “maybe“ swimlanes per Compass Components. We also consider adding standard components (Component field on issue Level) and let users configure whether to use Jira Standard Components or Compass Components. # Release Management App for Compass [https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/3315957761](https://releasemanagement.atlassian.net/wiki/spaces/RMC/pages/3315957761) > Macro (include)