In this release, you will mainly discover:

Price change

We're increasing the price of Requirement Yogi, for 3 reasons:

Confluence ServerData Center
TierConfluenceRY - 2018RY - 2019Confluence DC

Requirement Yogi DC

10 Users$10$10$10--
25 Users


50 Users$3500$500$900--
100 Users$6400$900$1600--
250 Users$12,400$1800$3100--
500 Users$19,300$2500$4850$12,000$4,850
1000 Users---$24,000$6,000
2000 Users$22,800$3500$5700$48,000$12,000
10.000 Users$29,100$4500$7500$130,000$24,000
15.000 Users

20.000 Users

25,000 Users


Confluence Server customers who have bought the product for the first time before 30/05/2019 can benefit from the old price until 30/05/2020. Please ask our support for a voucher, using the name of your company, and we will provide it.

Notes for administrators

We've worked on the reindexing algorithm

If you notice a change of performance, please notify us. We've ran the tests (see Performance) and reach the same results, varying depending on the quantity of changed requirements, so we're confident we're not impacting your servers negatively. However, it may always happen that we underestimate some scenarios, so please tell us about any issue.

We aim at obtaining the Data Center certifications, so the performance will keep improving in the following months. See Data Center strategy for Requirement Yogi.

Global limit

It is now possible to set a global limit which is used everywhere. The default is 12,000 requirements in any batch, 2,000 by default in the UI, and 4,000 for import. See Global limit if you are interested.

We haven't implemented the global limit yet on the Coverage and Dependency matrix.

Excel import

We've introduced the Excel tab, to import requirements from Excel files.

See Excel Import if you are interested.


We plan to change the permissions.

We used to rely on the EXPORT permission of the space, to determine the visibility of the Coverage, Dependencies, Traceability and Excel tabs. At the time we chose the "Export" permission, although the name doesn't fit, because it matches the performance profile of the export: Those features require a lot of processing or I/O power, and exporting a space also requires a lot of power.

Since we've implemented the Global limit, we believe there is no reason to require this permission anymore, since we've found a way to limit the impact of those features on other users. We plan to drop this permission in the next release.

Be prepared, in an upcoming release, to have those tabs appear for all users.

Changes in the Test & Compliance module

Changes in the RY for Jira module

List of Jira issues