Page Comparison

...

...

...

Atlassian has announced they are retiring the Server versions of their products: https://www.atlassian.com/blog/announcements/journey-to-cloud

• Every "server" customer needs to move to the Cloud,
• Privileged customers will go to Data Center versions: Self-hosted inside the customers' network, clustered with several nodes, it resolves problems like storage location, private domain, private network.

DC is now the Cloud++ version, rather than the Server++ version.

Requirement Yogi plans

In November, we have published the Cloud version we were working on, in emergency after Atlassian's announcement.

 = Already available.

...

The first version is very simple, but contains the essential parts of the workflow:

•  The requirement macro,
•  The search,
•  The properties and dependencies,
•  The traceability matrix.
•  A wizard to transform a page into a Requirement Yogi page.

It will at least help customers plan and visualize how to migrate their data. But it lacks the following features:

• The little popup. Since it is not possible to do it, the popup will be replaced by a full page. This still allows customers to navigate across requirements and build traceability matrixes, which is the essential part of the product.
• Saving the traceability matrix,
• The baselines,
• A migration tool from Server to Cloud,
• Requirements in vertical tables, the RY Property macro (hidden properties, coloured requirements), dictionaries, the RY Reports macro, the traceability matrixes in pages.

This first version is included in the Security Bug Bounty, which ensures the trust of customers.

...

•  Ability to save the traceability matrix.

...

• Integration with Jira.

...

This is not contractual:

• Baselines. As opposed to our first announcement, Baselines won't be available on the cloud. We will re-evaluate this decision once we have more maturity with our cloud app.
• A migration tool. However, traceability matrixes will never be able to migrated, since the underlying data is entirely different.

...

 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.

...

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

...

There was no automated migration path to the cloud until 3.5.0. If you were using Requirement Yogi 3.4 or lower, this page explains how to transform requirement keys to text, then transform them back to keys in the Cloud.

Before migrating to the Cloud

Things to know:

• We don't have baselines on the Cloud. It is a younger product with fewer features.

• 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.

• Both Jira and Confluence should be in the Cloud, or on Data Center, but we can't "mix" requirements from both instances.

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.

1. 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.

Be aware that Confluence Cloud can only connect to Jira Cloud, and Confluence Data Center only to Jira Data Center. It is not possible to migrate one side, then another.

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.	Image Added
Then, use the page to remove the macros from all pages and replace them with simple text:	Image Added

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.

2. Migrate

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

3. Transform the pages again

4. Recreate the Jira links

After transforming the pages:

• Go to Jira,

• Setup Requirement Yogi in Jira,

• Go to each Jira issue and recreate the links to Confluence requirements.

All Done!

As of January 2022, here is our next milestones for the Cloud:

• Better transformations for pages. We want to make it possible to transform documents the most easy way possible.

• Certainly features such as vertical tables, requirements in paragraphs, and improvement of the traceability matrix.

• The next major feature after those will be the baselines.

Features which won't be available:

• The Alt + Shift + R shortcut won't work in the Cloud. We have a wizard to assist with automatically replacing requirements.

• The

...

• inline popup, as it used to exist for Server, is replaced by a full page in the cloud, which requires clicking on it.

• The coverage and dependency matrixes, which wasn't popular. The traceability matrix retrieves the same results in a better way

...

Pricing

Pricing is slightly different on the cloud, but we'll make it as close as possible to the Server version: $1 per user.

However, we must make the Jira part paid as well, since it is a non-negligible scalability issue: $0.5 per user.

This roadmap is not contractual. We can only promise our team is 75% dedicated to Confluence Cloud, 25% dedicated to Data Center, but there are numerous uncertainties.

...

• .