How do people feel about the "next chapter" for Compass?

[Keith Furnell]

Well I guess this explains why there's not been much Atlassian activity here lately:

https://www.atlassian.com/blog/announcements/the-next-chapter-for-compass

The gap with respect to Jira integration seems significant:

https://support.atlassian.com/compass/docs/migrate-from-compass-to-dx/#Feature-comparison--Compass-and-DX-Fabric

[Gene Culling]

I haven't tried out DX, but I did feel like Compass was not fit for all my goals, or would have required a lot of work to customise it to work well for me. At least part of what I would have wanted to use it for is environment monitoring, tracking deployments + uptime, so I could link it back to work that was deployed. These might be outside of what the goal for Compass was, but I feel like it's an important part of DevOps

[Dave Mathijs]

Hi @Keith Furnell 

I found the DX "news" at Team '26 a bit underwhelming and was expecting more news, features and capabilities after the initial announcement (DX is joining Atlassian) in Barcelona last year  Feels like Atlassian is already ditching the short-lived Compass app that didn't gain much traction due to the configuration complexity.

DX has no official Atlassian Documentation yet, and the Software Collection page on the Atlassian website only refers to a Contact Sales button for more info.

[Martin Runge]

Hi @Keith Furnell

Yes, Atlassian is shifting the entire product identity to the DX platform. I like the goal of merging component tracking with developer productivity metrics in one place. For those using Compass, I am curious about the guided runway until December 2027, when access to standalone Compass ends.

To address the gaps you mentioned, Atlassian is rolling out dedicated onboarding and migration sync tools. These tools automatically port your Compass components as DX "entities" and map Atlassian Teams to DX Teams.

Ultimately, Compass is evolving from a standalone internal developer portal (IDP) into a foundational data layer for Atlassian's broader engineering management platform. If you're doing a POC like @Richard A_ Michaels, the main hurdle will be how those ported catalogs behave as native DX entities.

[Richard A_ Michaels]

I'll be taking part in a POC for the DX product.  We have Compass now and it took some work to get our engineers to get their services into the system.  One of our core goals was to link all engineering work items to the corresponding service.  We also had intention of linking our change and incident tickets to those same services to get a full picture.  Since DX doesn't integrate with Jira, that linking can't be accomplished.  With December 2027 being the EOL date for Compass, my hope is they will prioritize getting the integration done to ensure that functionality is available.

[Chethan GR]

I haven't tried out DX yet, but I'm looking forward to use and learn more about it.

[Tomislav Tobijas]

I was talking with one tester/half-user of Compass the other day and I've asked them about this. They said they even had DX demo-ed by Atlassian, but that Compass would even fit better in their case, as it's relatively simple compared to DX. DX is powerful (maybe even too powerful at this stage), and probably they won't be migrating anything or moving to DX in the foreseeable future 👀

I've just also got to the landing page of DX. Haven't explored much myself, but I would like to see more demos (baby steps) for the app + integration with Atlassian tools and Teamwork Graph (especially to be embedded in Atlassian Administration). 🤔

Lastly, I've completely missed this blog post/announcement and was surprised that it wasn't published here on the forums as well. I've asked if someone in Atlassian can forward this request to Compass/DX teams, so hopefully it will resurface in this group as well, with maybe even some additional info and insights (timelines and such).