Release 4.3 – Performance improvement for Jira fields in the traceability matrix

Contents of the release

This is a small release. We’ve just made it a major release because there are 2 small risks (see at the bottom).

• RY-1885 Indexing v2: Like in Indexing v1, requirements in vertical tables are considered “parents” of all following requirements on the page.

• RY-1869 Traceability matrix: For customers with thousands of Jira fields, we’ve greatly improved the performance of the matrix by only requesting the necessary fields. If you notice any change of behavior of the matrix, please communicate with us

• RY-1881 Following our React refactor in 4.2, we’ve removed any remaining link to the old UI,

• RY-1888 Upgraded our libraries

  RY-1889 Cloud migration: Baselines can be exported even when Confluence is in read-only mode.

Notes to administrators

In 4.3, we’ve upgraded all the plugins and reworked the communication between each others. If you are using other Requirement Yogi plugins (Yogi-Comala integration or Test & Compliance):

• Please either upgrade all our apps to 4.3.x,

• Or remain on 4.2.x for all of them.

Thank you!

Also, Confluence 8.5 is end-of-life, please upgrade to Confluence 9.2 as per our Compatibility matrix.

Risk assessment

• Traceability matrix and Jira: While working on RY-1869, there is a small risk that we didn’t see advanced configurations of the traceability matrix, in which case users may not see related Jira issues or their fields. If so, please communicate with us.

• Dependencies between vertical and horizontal tables: RY-1885 reintroduces a behavior that existed in Indexing v1, but has been absent for the last 2 years. Some users have re-implemented parent-to-child dependencies between vertical and horizontal tables by manually adding those links in all lines of all horizontal tables.

  • We apologize to customers who have done this work, and are now facing the re-introduction of this feature in v2,

  • We initially expected not to implement it in v2, and not to implement it on the Cloud,

  • But there was a lot of demand. It was re-implemented in the Cloud, so we’ve ended up aligning the Indexing v2 with it.