Transition to the cloud

Requirement Yogi plans

We were already preparing a solution for the cloud, which we are going to rush into production in the next ~3 weeks.

First version, mid-November

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

• The requirement macro,
• The search,
• The properties and dependencies,
• The traceability matrix,

It will at least help customers plan and visualize how to migrate their data. But it will lack those 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.

With this first version, we'll be able to launch various programs including the Bug Bounty, which we estimate is necessary to continuously have people who audit the security of our customer's data.

We have the architecture to move the data storage to the geographic zone of your choice, but that choice won't be visible in the UI. Contact us if interested. We still have a stub of information per customer which needs to be in our central database.

In the following months

• Ability to save the traceability matrix,
• Integration with Jira,
• Baselines. They will be implemented differently than on Server/DC, to better match customers' expectations. Experts expect baselines to be a bag of requirements in various versions, and a requirement only changes version when it is modified. That is what we will do.
• A migration tool. Expected for summer 2021. We'll migrate pages, macros and baselines. Traceability matrixes will never be able to be migrated, since the underlying data is entirely different.

Features the Cloud won't have the first year

• 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 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 an RY Reports macro on a page into a static table, thereby "freezing" the contents of the report.

Features the Cloud won't have

• Requirements must be defined in tables. Table format will be strict, requirement keys must be in the first column, the second is the title, and properties/dependencies are in subsequent columns.
• The Alt+Shift+R shortcut won't work in the cloud. To transform a page and add macros, we will display a wizard.
• The popup will not be available in Cloud.
• The Coverage and Dependency matrixes, which no-one was using. The traceability matrix does the same thing, better.
• The RY Property macro (hidden properties, coloured requirements), dictionaries.

Features that we are pumped to build in the cloud

• A document importer. You will be able to map fields and— We can't promise in advance, but we believe you will be happy with it.

Pricing

Pricing is slightly different on the cloud, but we'll make it as close as possible to the Server version: $1 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.

Once again I would like to express to you my solidarity towards all the teams who are currently being impacted by the transition to the cloud, and who will have to work overtime to migrate. It caught us before we had a decent solution, but we will pivot and make it happen, with a few rough edges.