Versions Compared

Old Version 9

changes.mady.by.user Mileva Briand

Saved on

compared with

New Version 10

changes.mady.by.user Mileva Briand

Saved on

Key

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

...

Step 1 - Export the entities to a temporary table

ConfluenceJira


Requirement Yogi lets you choose:

  • The scope: It is possible to restrict the export to a single Confluence space. Restricting by Jira projects is not supported (The screenshot below doesn't contain the field 'Project key' anymore).
  • The backup key: In order to avoid collisions when 2 administrators are working on imports/exports, you can specify your own key. It doesn't matter what the key is, please keep it simple.
Image Modified

This step only copies all data into a single table, in preparation for the export. The table is as big as the entire database, therefore it will be important, later on, to empty this table.

None of those long-running task should be interrupted by, for example, a Confluence restart. If it happens, please restart the step.

Of course you can leave the page. If you lose the link, you can find the progress of the task in the "Queue" tab.

Image Modified
At the end, we suggest to write the file to disk. If you have lost the link to this progress screen, you can perform this operation using the main menu:Image Modified




Step 2 - Write to disk

Note: This step can be skipped if you prefer (or need) to copy data manually. In such situation, please copy the contents of the tables AO_32F7CE_DBBACKUPITEM and AO_32F7CE_DBBACKUPMAPPING across to the target Confluence/Jira instance, and skip to step 5.

...

For each entity (space, issue, project key, user...), you will have to provide the ID of the new entity in the target database, so that Requirement Yogi can "plug" itself to those entities. Fortunately, we provide an automatic mapping, which will lookup for the ID in the database, check that the title/details of the entity match the previous names, and/or it will attempt to find the new entities (such as the issue, based on the issue title). If an automatic mapping can be found, the status will be "MAPPED_AUTO". It is still necessary to check the value and eventually map manually. 

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.
Image Modified



Once all entities are mapped, you can proceed to the next step.

...