...
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
...
| Status | ||||
|---|---|---|---|---|
|
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 .
Our apps are migrating from Connect API to Forge
Atlassian requires us to migrate from the framework Connect to Forge (Announcement here). Before version 2.2.0 our apps were based on Connect, we have now migrated to Forge.
What you need to do (as an admin): Nothing.
What you need to do (as a user): Nothing.
What changes for you now: Nothing.
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.
Requirement Types: Fix on the count of requirements, and the selection of properties.
Queue (for Admins): Improvement on pagination
Cleanup tasks: Improvements
RY for Jira panel: Improvements - removed search when they are no requirement links)
History: Added the number of Jira dependencies in the History panel (Requirement Detail)
Technical:
Improved accuracy of API error messages