Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Confluence
Teams
, (opens new window)
Requirement Yogi (Data Center)
Results will update as you type.
  • Getting Started - Tutorials
  • Administrator's guide
    • Configuration
    • Maintenance guide
    • Limitations
    • Migration to the Cloud
      • FAQ & Troubleshooting
      • Transformation - Migrate Server macros to Cloud
      • Difference between RY Property macro and RY Configuration macro
      • Manually migrate RY Report macro
      • Migrating Baselines from Server to Cloud
    • Requirement Yogi Cloud vs Data Center
    • Backup, import and export of Requirement Yogi data across Confluence and Jira instances
    • Database schema
    • Changing Applinks
    • Performance
    • Copying, Splitting and Moving pages
    • Choosing the indexing engine
    • Notifications
    • Data Center SLA / Escalation process
    • History - Administrator's guide
  • Features
  • Requirement Yogi for Jira
  • RY Testing and Compliance
  • Integrations
  • APIs
  • Release notes
  • Archives (Legacy Features)
    Calendars
You‘re viewing this with anonymous access, so some content might be blocked.
/
Manually migrate RY Report macro
Updated Sept 04

    Manually migrate RY Report macro

    Context

    The main goal of this page is to present every details of the Data Center macro requirement-report and its equivalent in the Cloud. Note that the requirement-report-pages does not have an equivalent on the Cloud.

    As Explained in RY Reports, the RY Report macro can be added to your Confluence page with the shortcut /req, or by copying and pasting a saved Traceability Matrix URL in a Confluence page.

    image-20250826-135432.png

    Feature details

    Now let see the different features of this macro and how to migrate it in Requirement Yogi Cloud.

    Option 1 - If the RY report comes from a saved Traceability matrix

    The first step of this manuel migration is to create a Traceability Matrix (Traceability matrix) in the Confluence Cloud with the same data as your DC report.

    Steps to follow

    Description

    In Data Center

    In the Cloud

    Steps to follow

    Description

    In Data Center

    In the Cloud

    1. Create equivalent Traceability Matrix in Confluence Cloud

    • If you have access to your Data Center instance:

      • In edit mode, click on the RY report and view in Traceability.

    When a RY report has been copied using a saved traceability matrix, the data is dynamic.

    Screenshot 2025-09-01 at 11.53.12.png

     

    In the Traceability Tab, you can see the saved query () and the columns ().

    Traceability Matrix Data Center.png

    In the Cloud, go to the Traceability tab, and copy the query in and display the columns using the cog menu in the table header ().

    Traceability Matrix Cloud.png

    2. Insert the saved matrix into your Confluence page

    Go in your Confluence page in the Cloud where the RY Report macro has not been migrated and insert the saved matrix as replacement using the /reqreport shortcut.

    Once inserted, you can filter by your saved matrix name, then select the matrix you want to insert and validate.

     

    image-20250827-065826.png
    image-20250827-094733.png

    Option 2 - If the RY report has been created from the page

    Create equivalent Traceability Matrix in Confluence Cloud

    Steps to follow

    Description

    In Data Center

    In the Cloud

    Steps to follow

    Description

    In Data Center

    In the Cloud

    Step 1: Filter wanted requirement with query

    You can quickly copy the query present in the Data Center RY Report macro into the Cloud building a traceability matrix with the equivalent query.

    image-20250826-140634.png

     

    Go to the Traceability Matrix tab.

    image-20250827-063134.png

     

    Step 2: Add other columns

    Now you can reuse the properties listed in the box Columns from your RY Report and add them to your Cloud matrix with with the cog menu in the table header().

    image-20250827-063903.png

     

    image-20250827-063918.png
    image-20250827-063930.png

     

    Step 3: Save the traceability matrix built to insert it in pages

    Once your traceability matrix has been created on the Cloud, you can save it by clicking on the Save As button. Name it, and set the permissions to allow other to see your traceability matrix.

     

    image-20250827-064044.png

    Options: Headless table

    If you selected the option Headless table in Data Center, you have to unselect the two options Show title and Show description that is the closest equivalent in the cloud allowing to have the less data around your table.

    image-20250827-100331.png

     

    image-20250827-100316.png

     

    Options: Use the last requirement and Use the last requirement definition

    Also works if your query is for the current baseline ($currentBaseline).

     

    This will override the search query and be used like a variable where the columns will show information from the last requirement (link or definition) in the page, or the last requirement definition only.

     

    On the cloud, you can replace this option by creating a traceability matrix with a query containing a variable (using the syntax ${variableName}) see more details here https://docs.requirementyogi.com/cloud/report-macro#Reportmacro:Insertamatrixintoapage-Usetemplatevariables).

    Limits

    There are some options which cannot be replaced on the Cloud:

    • Count.

    • Show all versions: but you can use a query to display multiple versions like baseline ~ % or variant ~ %.

    • Requirements from this space only: it’s the default behaviour in the cloud.

    • Limit : there is no limit as the cloud macro has a Load more button.

    • Sorting.

    {"serverDuration": 13, "requestCorrelationId": "6095a15bb18243b0905ec699032c9ce5"}