September 2025

ONGOING Notification regarding performances

We have been experiencing rate limit errors triggered by the Atlassian platform. We're working with the Atlassian support to resolve these ongoing difficulties as soon as possible.

You can try to improve your performances by manually migrating your largest pages to our Forge macros: Guide to migrate Connect macros to Cloud.

• You may have seen some weird behavior in your PDF exports. This issue was caused by the migration from the Connect macro to Forge. This issue is now resolved.

NOTIFICATION Migration of our Connect Macros to Forge

As per our migration announced in April 2025 Atlassian requires us to migrate from the framework Connect to Forge (Announcement here). We have migrated our macro ‘Requirement Yogi Definition’ to forge. There is no change for you in terms of features because it is exactly the same but it may explain some behaviors such as:

• Slow loading of macros: this is related to our latest ongoing notification September 2025 | ONGOING-Notification-regarding-performances .

• Order of the macros when typing /req : the definition macro is no longer the first one.

Minor improvements

• Migration improvement: you can now migrate requirement-properties macros to the Cloud.

  • We have added a transformation to the rule 'Migrate server macros to Cloud', and it will now transform the requirement-properties (DC) present in your page to a RY configuration macro.

  • Please read this guide to make sure you are aware of the details and differences in use: Difference between RY Property macro and RY Configuration macro .