Page Comparison

Confluence* DC** instance → New Confluence DC instance

Export and reimport a whole instance, with all the data.

_{* Same with Jira}

_{** Server and Data Center are both supported.}

Yes, it is supported.

• We recommend to use the same RY version on both sides (and we support a small range of versions).

• Please perform the Confluence-level import first, so pages, spaces, etc. already exist in the destination,

• Please create the application links, and set them up in the RY administration, before starting the RY import,

• Requirement Yogi settings will be imported.

• Page IDs, user keys, etc. must be remapped manually. This will be a long and mundane operation on your side.

• During the mappings, you can even change the space keys.

Note that Confluence and Jira are imported separately, therefore:

• After a Confluence reimport, perform a Jira reimport.

Confluence DC → Same Confluence DC, but later in time.

Yes, but there is no reason to do that.

• Please simply backup your Confluence instance using a way recommended by Atlassian.

Confluence DC space → another Confluence DC instance.

Ideal for merger-acquisitions,

Ideal for centralization into a large Confluence/Jira DC cluster.

Yes, it is supported.

• Same specificities as above,

• The global entities (the settings) will not be imported,

• If there are pages outside the space pointing to these requirements, they will keep pointing to the old place.

Confluence space → New Confluence space with different key.

Rename a space

Yes, it is supported.

• Please have the new space with the page IDs ready, before starting the RY import,

• Requirements can even exist in both spaces after import, but Jira links will only point to one of them.

• Jira links won't be updated, and this will be a problem. Please export-then-reimport the Jira data as well, mapping the space key with the new one.

Backups

No, this is not supported.

• We require the same version on both sides, and it may take some back-and-forth between the two sides,

• Confluence data is not part of the RY backup, so you would have to perform a Confluence backup anyway,

• It is not a sane way to perform backups (backup size, process, etc.).

Migrate from DC to the Cloud

Yes, you can migrate macros and Jira links, but we do not support other RY data (baselines etc.). Find more information here: Migration to the Cloud

Migrate from the Cloud to DC

No, this is not supported yet. Same, we're hoping to do it.

A space is renamed

Requirement entities will be fine, but:

• Cross-space references (Pages outside the space) will keep pointing to requirements in the old space. There is nothing we can do, since we're not touching the data outside the space. You will have to edit the XML of pages, directly in the database.

• Jira links will point to the old space. To avoid this, export-then-reimport the Jira data as well, and map the space key. This is better supported than page-to-page cross-space references, since there is no XML to edit in Jira issues.

• The history of Jira issues will still reference the old space keys, in case they have changed.

A Jira project is renamed

Same as above: Please also update the references in Confluence, since there are links to Jira, and this can be performed by exporting-then-reimporting the Confluence side.

Requirements are moved to a new instance

No difficulty, you just have to remap to a new Applink URL.

All page IDs have changed.

This happens when you import on a new Confluence instance.

• You will have to look for the page with the same title, for each page ID and page version.

• It is better if you gain SQL access to the database and update the table AO_32F7CE_DBBACKUPMAPPING in SQL, so you can retrieve the new page ID with a subquery.

There are requirements in Excel files.

We will reimport as-is, but the Excel attachment IDs will be wrong, since we do not remap them. Links to the Excel files will be broken, but the requirements will still exist.

1. Export to a table*

2. Write the table to a CSV file

3. Delete the temporary table

4. Load the CSV file into the temporary table

5. Perform the mappings
(automatically, then manually)

6. Import the data

7. Re-start at step 5,
or delete the temporary table

Steps 2-3-4 → You can bypass the CSV file by copying the data yourself to the target DB.

Destructive step

It erases the target data and replaces it
with the import.

Here are the possible statuses (matching the database column AO_32F7CE_DBBACKUPMAPPING.STATUS):

• (null): Not mapped yet,

• UNMAPPED: Couldn't find a match,

• MAPPED_AUTO: Displayed as "MAPPED" + an exclamation mark "!" - It was guessed by the software,

• MAPPED_MANUAL: Displayed as "MAPPED" + a green checkmark - It was either set manually by the user, or the user clicked the button "MAPPED" to confirm a "MAPPED_AUTO" value.