Versions Compared

Old Version 7

changes.mady.by.user Adrien Ragot

Saved on

compared with

New Version 8

changes.mady.by.user Adrien Ragot

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Tip
titleEveryone moves!

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.

Tip
titleCloud documentation

Our Cloud version 1.0 is published, here are the docs: https://documentation.play-sql.com/display/RYC

Requirement Yogi plans

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

(tick) = Already available.

...

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

  • (tick) The requirement macro,
  • (tick) The search,
  • (tick) The properties and dependencies,
  • (tick) The traceability matrix.
  • (tick) 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.

...

  • (tick) Ability to save the traceability matrix.

...

  • (tick) 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.

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.

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.

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.

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:

Image Added

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


Image Added

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

...

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.

Info

Any question? Raise a ticket!

...

  • .