Versions Compared

Version Old Version 14 New Version Current
Changes made by

Mileva Briand

Mileva Briand

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Status
colourGreen
titleNEW
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.

Status
colourGreen
titleNEW
Data Residency

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

Expand
titleRecap 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 security@r-yogi.com.

  • 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

    Status
    colourRed
    titleNOT POSSIBLE AT THE MOMENT
    .

    • For previous installations (customers who installed the app before ), 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 ), 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.

Status
colourGreen
titleImprovement
Key suggestions

...

  • 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

...