Content Comparison

...

Overview of the migration process

1. Perform the prerequisite steps,

2. Open up the migration endpoint in Requirement Yogi Cloud (both Confluence and Jira),

3. Migrate the Confluence data,

4. Check and acknowledge the warnings and errors in Requirement Yogi for Confluence Cloud,

5. Migrate the Jira data,

6. Check and acknowledge the warnings and errors in Requirement Yogi for Jira Cloud,

7. The migration is done.

...

Required steps before migrating

You need to:

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

2. Same for the JCMA plugin in Jira;

3. Update Requirement Yogi Server to the latest version, (minimum 3.5.1 for Confluence, and 3.5.2 for Jira);

4. Install Requirement Yogi on Confluence cloud, and on Jira Cloud;

5. The app automatically creates a Requirement Yogi user. Here are the steps to check the user can view and create pages in your spaces:

   • In Confluence Cloud → Settings → Security → Global Permissions:

     • Requirement Yogi for Confluence Cloud is expected to be in a user group in the User groups tab,

     • Requirement Yogi for Confluence Cloud is expected to be listed in the Apps tab,

     • If you need help, see the screenshots in Section 1.

   • In Confluence Cloud → Settings → Security → Space Permissions:

     • The user group assigned to Requirement Yogi is expected to be listed in the Default Space Permissions, with permissions to view and add Pages (Confluence doesn’t distinguish between add and edit permissions).

     • Individual spaces where you want to use Requirement Yogi are not expected to override the default space permissions for the RY user group.

     • If you need help, see the screenshots in Section 2.

6. Check page restrictions. If there are page-level restrictions, then the app can’t view/edit the pages with requirements. Two solutions:

   • Either you manually include Requirement Yogi in those page restrictions to edit those pages, but that requires that you edit each page restriction,

   • Either you just let the migration fail, then use our Pages tab, searching for type=page AND macro=requirement AND ryc_isMigrated != true in CQL, and migrate all those pages manually in the future.

...