Release Management: Migration to Atlassian’s Forge Platform & Upcoming Breaking Changes

Dear Customer,

We hope this message finds you well.

We’d like to share an important update regarding our transition to Atlassian’s Forge platform (Run on Atlassian) and notify you about upcoming changes that may require action on your side.
Earlier this year, we migrated our Connect App to Connect-on-Forge as the first step toward a full migration to Forge by early 2026. This transition brings significant benefits, including:

• Support for data residency

• Enhanced security and compliance

• Tenant-level data isolation

• Compatibility with Atlassian Government and Isolated Cloud environments (when applicable)

Our aim is to ensure this migration is seamless for you — with no disruption or manual effort required, ideally just a simple app update via the Atlassian Marketplace.

That said, we have identified one area where breaking changes are expected, and we want to give you early notice to ensure a smooth transition:

⚠️ Changes to API Usage

• API Endpoints will move from a multi-tenant to a single-tenant model. As a result, endpoint URLs and some of the API signatures will change. We aim to maintain the same method signatures where possible.

• API Tokens may change due to Atlassian’s shift toward a new access token model, incorporating scopes and other modern standards.

If you're currently using our APIs via Jira Automation, external systems, or custom integrations, we kindly ask that you open a support ticket describing your use case. This will allow us to form a small working group to support you through the transition, share technical details, and coordinate timing as needed.

We will keep you informed throughout the transition process and will share the finalized API endpoints and models as soon as they are available.

Thank you for your continued support!

Share your API use case

Best regards,

Support Team
Release Management Apps
http://www.releasemanagement.app