Migration to Forge

Rewrite the app using Forge APIs

Done

Published, mid-January 2026.

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

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.

URL changes

Done

All our URLs must change 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.

Migrations from Data Center

Done

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

The migration will bring some benefit (No more “Not authenticated” error). However, the code was rewritten using the new Atlassian APIs, so we expect customers to discover new forms of bugs.

Byline not loading

Please raise a ticket

The byline is the little dialog accessible through the Requirement Yogi icon at the top of pages.

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.

Search and traceability timeouts / size limits

In development

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

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 must perform specific developments to view reports asynchronously and fit within Forge’s tight limits, which will take weeks.

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

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 https://confluence.intranet.requirementyogi.com/wiki/spaces/RYC/pages/2823389213/September+2025#ONGOING-Notification-regarding-performances .

There are two sides of the problem:

• Not solved To be honest, according to Atlassian’s explanation, we understand Atlassian’s solution only fixes the appearances, while not solving the problem, and their implementation will cause major problems down the line,

• In development Nonetheless, because Atlassian told customers it solves their problem (and passes it on to vendors), we’ll have to perform the developments to support this new API. Those developments are underway.

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