June 2025

NEW Requirement renaming

You can now rename your requirements!

Look for you requirements through the RY search, use the checkboxes to select requirements you want to rename. We detect automatically the common prefix and suffix that you want to rename, but you are free to override them according to your needs. You just have to check automatically that it suits you.

Then your requirements will be renamed, definition macros and links will be updated in Confluence pages as well.

NEW Data Residency

Requirement Yogi now supports Data Residency in Ireland, and United States. Please find more information here:

Recap of Data Storage and management

The app processes and stores the following types of End-User Data:
- User-created content: requirements, properties, dependencies, rules, variants, etc. and their history.
- Excerpts and metadata of Confluence pages and Jira issues that are used to extract requirements.
- Administrative data: instance ID, feature discovery, background jobs, etc.
App supports data residency and stores End-User Data independently outside of Atlassian products and services in the following locations:
- 🇮🇪 Ireland, 🇺🇲 United States of America
More information on the app’s data residency policy can be found in app’s product documentation or please contact the respective app partner at [email protected].
App stores the following types of in-scope end-user data:
- User-created content: requirements, properties, dependencies, rules, variants, etc. and their history.
- Excerpts and metadata of Confluence pages and Jira issues that are used to extract requirements.
- Administrative data: instance ID, feature discovery, background jobs, etc.
App stores the following types of out-of-scope end-user data:
- License information
- Any data involving the use of AI features
- Any data submitted to the support

⚠️ Please note the migration of in-scope End-User Data between data residency supported locations is NOT POSSIBLE AT THE MOMENT.
- For previous installations (customers who installed the app before 23 Jun 2025 ), the data migration is not possible and you will lose your data that is not stored in Confluence pages.(external properties, Jira issue links, saved matrices etc.).
- For any new installations (customers who installed the app after 23 Jun 2025 ), if your Atlassian instance is pinned in one of our supported locations (Ireland or US), the app will be installed in the matching location automatically.

IMPROVEMENT Key suggestions

Our previous key suggestions system had limitations. So we stepped back and built a new system filling the gaps of the previous one.
You will still be able to define any type of key you want, and suggestions will be based on your input, other requirements in the page, and across your space and variants.

For example, with the requirement CAT-002-REQ-004, we now suggest CAT-002-REQ-005 and CAT-003-REQ-001.

You can also find your key suggestions in the Requirement Yogi Manage section.

Find all key suggestions per variant
Reset keys to the last existing number
Delete key suggestions

Find more information in the docs. Enjoy this new experience and feel welcome to give us feedback on our support.

NEW Advanced Search now supports query for Jira projects

In Confluence, when using the search, you can now search for requirements depending on the Jira links project’s they belong to.

For instance project = ‘PROJ’ will only return requirements that are linked to Jira issues in the ‘PROJ’ project.

Head to the Search syntax page to learn more about how to search for requirements.

IMPROVEMENT Check the coverage of requirement to Jira links

In the Coverage tab, you can now select a requirement and check it’s coverage with Jira issues. You can filter with the relationship, type, and project.

Minor Improvements

Jira:
- The Jira requirement panel no longer shows all baselines of the requirements when filter is not specified
- Fixed the missing description in requirement link preview
Requirement Detail:
- We now render the Atlassian emojis in requirement description and properties
Traceability Matrix:
- Changed the name of the column ‘Variant’ to ‘Variant / Baseline’ as it displays both information.
- Improved the rendered Jira fields: ‘Linked issues’ and ‘sub-tasks’.
Baselines:
- Improved the UI/UX of the ‘Select requirements’ screen upon freezing requirements.
Modification Matrix
- When using the ‘Modified only', we’ve now included requirements that were added or deleted between one version and another.
RY Report macro can now embed saved Modification matrices.
History UI/UX:
- Display the change type in the history panel