Migration to Forge

Deployment of the Calculation macro to forge

Done

First step in the migration to Forge project.

Deployment of the Definition Macro to Forge.

Followed by RY report and Configuration macros

Done

Impact 1: Forge macros have performance issues. See troubleshooting for more information.

CCMA and JCMA now uses Forge framework

Done

The code was rewritten using the new Atlassian APIs, so the process has completely changed. Please ensure you’ve read the documentation to get the latest updates: Migration to the Cloud .

Data Center customers must upgrade the DC app to the latest version.

The migration will bring some benefit (No more “Not authenticated” error) but we expect customers to discover new forms of bugs

Deployment of front-ends tabs to Forge.

URL changes

Done

Impacts on the Details, search, traceability and other tabs.

All our URLs have changed for the Forge migration. The first change was performed on January 13th.

The URL of requirement details may change again to make them cleaner. If you want to be notified when we start to implement those changes, please reach out on the support.

All customers must upgrade the app to the latest version

Action required on January 20th, 2026

Administrators must approve the new permissions. The permissions of the app haven’t changed, but Atlassian has changed the permission granularity.

The upgrade is required, both in Confluence and Jira.

Removal of legacy Connect authentication methods

Done

This change means implies a lot of changes in the backend.

Impact 2: Users who didn’t upgrade the app to v4.4 will be disconnected.

We’re polishing the results, so please raise issues if any problem is still visible in February-March 2026.

Deployment of the Requirement Link macro to Forge

Done

See troubleshooting related to the slow performance of pages, and the byline (Migration to Forge | Troubleshooting )

Deploying all new Forge webhooks and clean up of the manifest

in progress

This is the end of the migration to Forge. Please feel free to raise a ticket on our support if you see any changes in behaviour.

Deployment of the
standalone app

in Development

Customers can view the data on our standalone app (included in the service), where we can deliver a full experience.

Search and traceability timeouts / size limits

In development

Workaround: Use smaller page sizes and/or less columns.

Workaround: Use the standalone app, where we can control the user experience.

1. Forge remote invocations enforce a 25s timeout (https://developer.atlassian.com/platform/forge/remote/essentials/#remote-contract).).

2. There is a size limit to 5 MB.

We have been working on a workaround by either developing our own app. Please see more information here: I receive timeouts errors in the Traceability - Forge limitation

Macros are loading slow

In development

Workaround: Split pages so they have fewer than 100 macros per page.

This is related to our latest ongoing notification September 2025 | notification Migration of our Connect Macros to Forge

There is an ongoing ECOHELP ticket opened with Atlassian so they can find a solution to improve performances → https://ecosystem.atlassian.net/browse/FRGE-1495 .

• This solution is still in development by Atlassian. When it will be released, you will be have to manually update the app in the Confluence administration (<v5.0), and activate the feature in the RY champion center > Configuration.

• If the Atlassian solution doesn’t work as expected, we have developed a Beta feature that will allow you to transform requirement macros to native Confluence smart links. This feature is under a feature flag. Please request the support to activate this feature for you, if it is necessary.

• MItigation You can split your pages so they have less than 100 macros per page. You can wait for static macros.

Byline not loading

Please raise a ticket

On large pages, the macros and the byline run in the same Javascript thread (not our fault) and sometimes, the Byline may load after all other macros, which means it timeouts.

Workaround: We’ve prepared a workaround whereby customers can use native Confluence links instead of macros. It is ready, please request activation with our support.

Clone large issues

No solution by Atlassian

When cloning issues, Requirement Yogi copies the links to requirements.

Unfortunately, Atlassian doesn’t send events larger than 200kB and drops them without notification.

In this situation, Requirement Yogi links are not initialized in cloned issues. Please add them manually.

Reference: https://developer.atlassian.com/platform/forge/events-reference/product_events/#known-issues