Skip to end of metadata
Go to start of metadata

Data Center

  • Customers who transition from Server → Data Center have nothing to do.
  • Customers who transition from Cloud → Data Center will face difficulties: We don't have any migration path for it.
  • Customers who transition from Data Center → Cloud: See below.

Before migrating to the Cloud

Things to know:

  • You will be disappointed with the lack of features on our Cloud version. Particularly, we don't have baselines, and we didn't spend 7 years polishing the UI until it was perfect.
  • On the Cloud, requirements must always be in the first column of tables.
  • It is more difficult to see the requirements on the Jira issues.
  • We don't have an assisted migration path yet. Baselines, traceability matrixes, reports, and links in Jira will be lost and have to be re-created manually.

Overview of the migration

Our only migration path is to remove Requirement Yogi, migrate, and use the transformation tool on the Cloud to transform the pages back.

Prepare the migration

The database

Before you start, perform an entire backup of the database and of Confluence. All the data of Requirement Yogi will be destroyed (baselines, traceability matrixes) and macros removed from Confluence pages.

In Jira

In Jira, nothing will be migrated to the cloud. We suggest exporting your data to Excel to be able to recreate it.

In Confluence

The first step is to replace all Requirement Yogi macros on pages, with simple text (the requirement keys).

In Confluence, go to the administration of Requirement Yogi, on the tab "Support" → Uninstallation wizard.

Then, use the page to remove the macros from all pages and replace them with simple text:

After this, Requirement Yogi will have deleted all the macros, but also all the records in its database, the traceability matrixes, history of requirements in baselines, links to Jira, etc.

Migrate

Use Atlassian's migration tools to move your pages to the cloud.

Transform the pages again

On the cloud, go through each page which contains requirements, and use the menu → Requirement Yogi to display the transformation dialog:

The transformation dialog should be preconfigured, just click "Transformation options" → "Transform and save" to transform the page.


After transforming the pages:

  • Go to Jira,
  • Setup Requirement Yogi in Jira,
  • Go to each Jira issue and recreate the links to Confluence requirements.


Done! Checkout our roadmap for the Cloud:

Not the first year

(error) We may develop those features one day, but certainly not before November 2021.

  • Vertical tables, which was a trick on Server to define a requirement as parent of the following ones.
  • The RY Reports macro, which allowed displaying search results in pages. Instead, users are invited to save their report and share it directly with others.
  • The "transform to static table" feature, which allowed transforming a report into a raw table in a page.
Not available

(error) We cannot / won't develop the following features for the Cloud version:

  • Requirements must be defined in tables, and the table format is strict (keys must be in the first column, the title in the second, and properties/dependencies in subsequent columns).
  • The Alt + Shift + R shortcut won't work in the Cloud. We have a wizard to assist with automatically replacing requirements.
  • The "RY Property" macro, which was specific to the server, replaced with the transformation wizard.
  • The popup with the requirement excerpt. It is replaced with a full page in the cloud.
  • The coverage and dependency matrixes, which wasn't popular. The traceability matrix retrieves the same results in a better way.
  • No labels