Versions Compared

Version Old Version 51 New Version 52
Changes made by

Mileva Briand

Mileva Briand

Saved on

Key

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

Using an old version of Requirement Yogi?

Please head to Migrating to the Cloud (before RY Data Center 3.5). Or better: Upgrade and use the easy guide below!

It’s quite simple!

Requirement Yogi Confluence migration is not necessary.

The transformation of Confluence pages after can be made after the migration, since all data is stored in the contents of Confluence pages.

As a result, please ignore Requirement Yogi when migrating.

...

This page describes how to migrate Requirement Yogi data Data Center to Confluence and Jira Cloud, using the official CCMA (Confluence Cloud Migration Assistant) and JCMA (Jira Cloud Migration Assistant).

...

Due to technical difficulties with the APIs, we have only just published the Phase 1 and 2 of CCMA. It will allow you to migrate :requirements, external properties and Jira links.

  • 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

on

  • to Jira issues + relationship

(tick) Ready

Traceability Matrices

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

  • Baselines

(tick) Ready with manual export/import.

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

  • Traceability Matrices

Other entities (Report macros and RY properties macro.)

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

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.

...

  • .

*We’ve stopped working on the migration of baselines and other reports, despite the demand for it, because it was outstandingly difficult and it was draining the resources of the company.

Overview of the migration process

...

See typical warnings in the Troubleshooting page.

...

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.