Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Introduced in Requirement Yogi 1.6

In this article we explain how to use Requirement Yogi to refine specifications from high-level business requirements to low-level technical specifications.

See the product page.


This release is especially focussed on the TC module, "Testing & Compliance". We're introducing:

  • Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.
     When running a test session, we can now add comments and raise Jira issues along with the pass/fail result.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  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.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  It is possible to copy and reset a test report, in order to run it again.

Minor fixes:

  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Bugfix: In RY Reports, null cells would contain the previous value instead of being empty.
  • Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Ability to transform a table into requirements by selecting cells. It brings the flexibility that the RY macro can be created in the second column, or that the RY macro can reuse the contents of the cell if they already contain requirement numbers.


  • No labels