NEW Coverage of your requirements
If you are looking for a way to check if your requirements have the correct dependencies, you are now able to cross-check requirement types and their dependencies, using the coverage.
Select two requirement types, and click on ‘Build Coverage’.
See on the left when your first requirement type is the parent of the second.
See on the right, when your first requirement type is the child of the second.
The graph showcases the dependencies between the two requirement types.
Save the report and find it back in the ‘Saved Matrices' tab.
Would like to know more? Check the documentation.
If you are having questions on what to / parent, from / children mean, read this page: https://confluence.intranet.requirementyogi.com/wiki/spaces/RYC/pages/2564128774/Requirement+dependencies#I-cannot-remember-what-TO-and-FROM-is-%3F-What-is-the-direction-of-dependencies%3F
NEW Baselines: Freeze your requirements
You’ve been waiting for it, and now it is live: You can now freeze your requirements over time.
Mark key milestones like Product Releases: When managing requirements, you may want to freeze requirements each time a release is made, so you can keep track of your requirement’s evolution. You will be able to answer to the question: “What was the exact requirement in Release 251".
Tag versions of requirements approved by your stakeholders or third-parties (FDA, ISO organizations etc. ).
Once a requirement is added to a baseline, it’s locked and frozen. No accidental edits. No confusion. Just a clean historical reference you can rely on.
Please see the documentation for more in-depths information: Baselines .
Minor Improvements
UI/UX :
External Properties: Improvements in the Requirement Detail.
Variants: Minor improvements on management page
Traceability: Improvements on total values displayed with external properties number.
Queue (for Admins): Improvement on pagination
Cleanup tasks: Improvements
RY for Jira panel: Improvements - removed search when they are no requirement links)
Technical:
Improved accuracy of API error messages