Warning: If you are using this version, in complement with Requirement Yogi and the Jira module, then please also upgrade the Jira module to 1.13.0 (otherwise a technical queue of messages will fill up).

• RY-243 If a test session mentions a requirement, and if you create a Jira issue in the test session, then the Jira issue will be linked to the requirement.
• RY-274 Bugfix: Test sessions now work on baselines
• RY-267 Message queue for changes on requirements between Confluence and Jira.

In this release, the most visible feature is to make it possible to raise Jira issues and write comments while we're completing a test session.

• RY-256 When running a test session, we can now add comments and raise Jira issues along with the pass/fail result.
• RY-202 For people who don't have Requirement Yogi and who write requirements in Jira (X-Ray users, namely), it is possible to create a test session based on the results of a Jira query.
• RY-255 It is possible to copy and reset a test report, in order to run it again.

• RY-255 In the "..." menu of the page, add the ability to copy a page and clear the test results.

Compatibility with Confluence 6.8.

Fix the popup in the page breadcrumbs, which didn't display in certain situations (depending on what other elements were displayed on the page).

For a fix of RY-225, please upgrade the Requirement Yogi app too.

• RY-219 Fix error when saving an RY Test macro and there is no requirement on the page. This requires Requirement Yogi 1.10.2.
• Also provide a default value in the blueprint creation dialog for the "relationship" drop-down.
• And ensure the blueprint always has 4 columns.

• RY-187 Tell administrators when they are using a different version of Requirement Yogi and RY Testing.
• RY-193 A global administration screen to manage the relationships and statuses
• RY-197 Various options to generate tests based on search results.

This release has all the necessary features to work independently or together with Requirement Yogi:

• The testing blueprint,
• The status macro,
• The byline item at the top of the page, which starts a live session where the user can change the macro status.
• The integration with Requirement Yogi