Versions Compared

Version Old Version 56 New Version 57
Changes made by

Mileva Briand

Mileva Briand

Saved on

Key

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

...

  • Requirements

    • As they are defined on Confluence pages, they will always be migrated, as well as their properties and dependencies.

  • External Properties.

(tick) Ready

  • Requirements links to Jira issues + relationship

(tick) Ready

  • Baselines

(tick) Ready with manual export/import.

Not within the CCMA but it is possible to manually export Baselines from Server and import them back to the Cloud.

  • Traceability Matrices

(error) No, and we’ve stopped working on it*

  • Other RY macros on pages

  • Requirement Types

(error) No, and we’ve stopped working on it*

  • For reports (requirement-report, requirement-report-pages), you’ll have to remove old macros and replace them with the RY Report.

  • Requirement-property, you’ll have to remove those macros, and use the RY Configuration instead.

  • requirement-baseline macros will not get migrated either.

...

💡 App migration can take a long time to run, especially if you have thousands of pages. On our test instance, the migration took 20s per 1000 requirements (1h30 for a sample of 220k requirements spread on 2000 pages).

3. Ending the Migration

How to check progress of the migration?

...

  • Errors and warnings are listed on the Requirement Yogi Migration Notification page (Admin access is required).

  • Errors on pages have a link to the page that generated an error. You can navigate to said page and manually verify if the migration was a success. If the migration wasn’t successful (ex: Requirement Yogi macros are shown as ‘Unknown macros’), you can manually transform those macros and mark the notification as “Resolved”.

Please do feel free to open a ticket to notify us of errors generated by the migration tool by raising a support ticket.

...

Acknowledge the migration task

In the end, ensure you acknowledge the Requirement Yogi migration task on the Cloud side. It is important, so that the migration task on the server side knows that Requirement Yogi is done.

...

  • On the Cloud, pages containing requirements must be migrated to the new editor experience, since we only have transformers for the new JSON/ADF storage backend, and not for the XML one. The migration will be triggered when we apply the transformation.

  • This “Phase 1 and 2” doesn’t import the RY Property, test macros, baselines, existing reports, and report macros to the Cloud.

Frequently Asked Questions

...

The migration of our Confluence app only includes External Properties, and a transformation of some RY requirement definition and requirement link macros from Server / Data Center to Cloud format.

What is not included in the Requirement Yogi migration ?

  1. Some RY macros are not migrated and cannot be transformed with the migration / transformation wizard:

    1. For reports (requirement-report, requirement-report-pages), you’ll have to remove old macros and replace them manually with the RY Report.

    2. Requirement-property, you’ll have to remove those macros, and use the RY Configuration instead.

    3. requirement-baseline macros will not get migrated because we do not have an equivalent on the cloud.

  2. Traceability Matrices and Requirement Types are also not migrated.

  3. Baselines are not migrated within the CCMA, but they can be manually exported and reimported if necessary. Please find the documentation for more information.

What is included in the RY for Jira migration ?

...