Moving Confluence pages or spaces
It may happen that you want to migrate Confluence spaces from one instance to another (Testing to prod, or else). Confluence has a feature called “Data transfer” that you can use.
If you want to migrate the Requirement Yogi data, you need to know a few things.
There are two ways data is stored: Within Confluence pages, and within the app. Not everything will be migrated if you copy, or move content from one instance to another.
What will be migrated?
Will be migrated (Stored within Confluence) | Will not be migrated (Stored within Requirement Yogi) |
|---|---|
All macros in Confluence pages
|
|
Steps to migrate
Follow the steps to migrate your data using the Atlassian Documentation: https://support.atlassian.com/organization-administration/docs/copy-confluence-data/ .
Once the pages are migrated, we need to receive an update webhook from Atlassian to index the requirements. You can trigger one manually by:
Editing / Updating the pages.
Click on the Yogi byline at the top of the page > Reindex
You can also create a transformation on one page with a rule that will not impact your pages (for example Migrate server macros to Cloud), save it, and then apply it on all pages with requirements in the page. (See docs: Transformation wizard: Transform your pages )
If you have too many pages or spaces to reindex please reach out on the support so we can assist you: https://support.requirementyogi.com/ .
You can check your requirements are indexed by clicking on one of the requirement macros, or by going in to the Space Apps > Requirement Yogi > Search.
For each data that we do not migrate, you will need to recreate the data manually.
Frequently Asked Questions
What will happen if I have links cross space or cross variant ?
When linking to a requirement, we will automatically link to a matching requirement in the space. Users can specify if they want to link a requirement defined in another space, or another variant.
If you have links to other spaces, those spaces will need to exist before you can link requirements to them. We should be able to point back to them.
Variants have unique IDs and when you will migrate your spaces, your variants won’t be recreated. You will have to recreate them manually, and then manually modify the variant of the links.
For both Variants and Space, you can use the transformation wizard to specify the target: Change the variant or space of requirement links.