/
[Forge Migration][2025-10-15] Forge remote and Impact on APIs access tokens

[Forge Migration][2025-10-15] Forge remote and Impact on APIs access tokens

Summary

We migrated to Forge remote as of Oct 25, 2025 Some previously generated Deep Links WILL STOP working. Short-term JWT access tokens will be deprecated shortly so Personal API tokens to be used instead. Personal API tokens will also become part of Standard Edition to foster our journey to Forge platform.

Still seeing “Upgrade“ request?

If after “Upgrade“ you still see “Upgrade“ request page please Ctrl+F5 (Command+R) your bowser and find “Release Management“ App in Apps section of Jira’s left menu.

Introduction

Earlier this year we articulated on the additional benefits for migrating from Connect to Forge platform and our initial thoughts on migration journey.

As of Oct, 2025 we are moving to Forge remote. What does it mean?

  • We will have NEW Forge UI that is different from Connect UI

    • So, most of the below changes are connected with this fact

  • Our backend will be partially Forge (Run on Atlassian) and partially will use Egress to access our backend hosted in AWS

Changes

Since we are migrating to the new platform we basically have new URLs for the main tabs and deep links so all previously generated links will stop working. Same time, Server-side links (namely API endpoints and Calendar export link) will remain operational and unchanged. There’s also an important change with regards to API authentication mechanism and short term API tokens to access our APIs outlined below.

Some previously generated Deep Links will stop working

Previously generated links to different Application tabs (with saved filters included) will stop working. You would need to create new ones.

image-20251013-150938.png

Deep links to versions and packages that you previously shared won’t work either. Please generate new ones.

image-20251013-151055.png

Deep links to release notes generation needs to be re-created as well.

image-20251013-153331.png

Permanent links will still work

Server-side links for Calendar Sync with Google, Outlook and Confluence Calendar will still work.

image-20251013-153638.png

 

Deep links from Issue Panel, Compass App and Rovo Agent will still work

Links from “Release Management“ Issue Panel, Compass App and Rovo Agent will work as expected.

API changes

Due to migration to Forge, Context JWT tokens with basic authentication will be decommissioned by the Dec 12, 2025 so the following link to get the context JWT API token will not be available:

https://YOUR_JIRA_INSTANCE.atlassian.net/plugins/servlet/ac/app.releasemanagement.rmcloud/board?classifier=json

This is a standard API authentication approach we used up till now throughput our documentation and automation use cases.

We are keeping one Connect module till Dec 12, 2025 for backward compatibility to allow approach with JWT API token to work.

If for some reason JWT tokens stopped working please change HTTP method from GET to POST. Or clean cookies if you are using Postman.

Luckily we recently introduced long-living Personal API tokens that should be used instead. To foster Forge migration journey we are making Personal API tokens part of Standard Edition of our App (available to everyone).

Please contact our support channels following the links below to discuss your specific use case of our APIs to elaborate on scope of the impact and advise on using Personal API tokens.