Versions Compared

Version Old Version 65 New Version Current
Changes made by

Mileva Briand

Mileva Briand

Saved on

Key

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

...

This document is mostly a checklist to ensure the task will be successful.

Follow each steps

...

Before the Migration

...

Starting the migration

...

Ending the migration

...

Table of Contents
minLevel1
maxLevel3
outlinefalse
styledefault
typelist
printabletrue

What will be migrated?

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 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 (since 4.2.14)

  • Traceability Matrices

(error)

  • Other RY macros on pages

  • Requirement Types

(error)

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

...

RY for Confluence

RY for Jira

1

On the Server/DC side, upgrade the CCMA plugin to the latest version;

On the Server/DC side, upgrade the JCMA plugin to the latest version;

2

Upgrade Requirement Yogi for Confluence Server to the latest version (minimum 3.5.1)

Upgrade Requirement Yogi for Jira Server to the latest version (minimum 3.5.2)

3

Install Requirement Yogi on Confluence Cloud.

Install Requirement Yogi on Jira Cloud.

4

Once the installation is complete, make sure you link your RY for Confluence and RY for Jira instances together, see docs.

5

Make sure permissions are set up so we can view and create pages in your spaces:

  • More information in the FAQ.

6

Make sure pages with requirements on your Server / Data Center instance are not restricted.

  • If there are page-level restrictions, then the app will not be able to view/edit pages with requirements.

  • See possible solutions in the FAQ.

7

Open the migration endpoints:

  • In Confluence Cloud > Manage Apps > Requirement Yogi Administration > Support > Activate the Server / Cloud migration for this instance.

  • This enables Requirement Yogi to receive notifications from the server migration assistant. You can close it once the migration is over.

Open the migration endpoints:

  • In Jira Cloud > Manage Apps > Requirement Yogi Administration > Support > Activate the Server / Cloud migration for this instance.

  • This enables Requirement Yogi to receive notifications from the server migration assistant. You can close it once the migration is over.

8

If you are using multiple relationships for requirement-issue links in Server / Data Center, make sure you create the same relationships in the RY for Jira Cloud administration as well.

...

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.

...