Versions Compared

Old Version 4

changes.mady.by.user Adrien Ragot

Saved on

compared with

New Version 5

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: selfSelf-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

We were already preparing a solution for the cloud, which we have successfully rushed into production In November, we have published the Cloud version we were working on, in emergency after Atlassian's announcement.

(tick) = Already available.

First version, mid

TimeFeatures
Mid-November

The first version

will be

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

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

will lack those

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.
With this first version, we'll be able to launch various programs including the

This first version is included in the Security 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

ensures the trust of customers.

December
  • (tick) Ability to save the traceability matrix
,
  • .
January
  • Integration with Jira
,
  • .
Features we are planning for the first year

This is not contractual:

  • 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
  • However, 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
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
an RY Reports macro on
  • a
page
  • report into a
static table, thereby "freezing" the contents of the report.Features the Cloud won't have
  • 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
. Table format will be strict, requirement
  • , and the table format is strict (keys must be in the first column, the title in the second
is the title
  • , and properties/dependencies
are
  • in subsequent columns).
  • The Alt + Shift + R shortcut won't work in the
cloud
  • Cloud.
To transform a page and add macros, we will display a
  • 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
will not be available in Cloud
  • with the requirement excerpt. It is replaced with a full page in the cloud.
  • The
Coverage
  • coverage and
Dependency
  • dependency matrixes, which
no-one was using
  • wasn't popular. The traceability matrix
does
  • retrieves 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.
    • 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!


    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.