Versions Compared

Old Version 40

changes.mady.by.user Mileva Briand

Saved on

compared with

New Version 41

changes.mady.by.user Mileva Briand

Saved on

Key

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

...

Requirements on pages

(tick) Ready

Requirements links on Jira issues + relationship

(tick) Ready (we do not migrate relationships)

Traceability Matrices

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

Baselines

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

Data is not migrated. In the Cloud we have variants, see the difference here.

Other entities (Report macros and RY properties macro.)

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

  • For reports, you’ll have to remove old macros and replace them with the RY Report.

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

Limitations

  • 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.

...

  1. Do it again for the Jira part.

    1. If you are using multiple relationships for requirement-issue links in Server, make sure you create the same relationships in the RY for Jira Cloud administration as well. (See docs for more information: https://requirementyogi.atlassian.net/wiki/spaces/RYC/pages/1804764144/Requirement+Yogi+for+Jira#Administrate-Requirement-Issue-relationships )

Starting the migration

If you have both Jira and Confluence, you will have to start both migrations. We recommend doing the Confluence migration first. We will still create links to requirements that were not yet migrated, but show a warning that the requirement was not found.

...