Use case
Mark key 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.
💡 Quick reminder:
...
How to create a Baseline ?
...
The description (in Confluence pages)
Properties (in Confluence pages)
External Properties (RY data. You can make the edition of external properties in baselined requirements available in the Administration)
Dependencies
Jira Links
Page links (link of the page version when the requirement was frozen)
Permissions
Create and edit a baseline: Users who have edit permissions on the space.
Delete baseline: RY champion and space administrators.
Limitations
The number of requirements per baseline is set to 30 000 requirements. Please let us know if you want to freeze more requirements than that number.
Frequently asked questions
How to check the difference between one baseline and current requirements?
At the moment, we do not have a comparison tool for baselines. In the future, you’ll be able to compare baselines using the Modification Matrix.
Can I link requirements or Jira issues to a specific baseline? How can I export my baselines?
For Jira issues, just like you used to do with the variants, you’ll be able to select a baseline in the version dropdown.
The link to baselined requirements in Confluence is To Be Released.
Can I import baselines from DC to the Cloud?
Without following CCMA, you can manually export baselines from Data Center and reimport them on the Cloud. Please follow this documentation page: Migrating Baselines from Server to Cloud.