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 ?
...
You can edit the name and the description of a Baseline by clicking on the edit button.
The content of the a baseline (, specifically the requirements ) will not be editable, the requirements it includes, will be captured and locked and uneditable once captured. These requirements are effectively "frozen in time". The living However, the living (non-baselined) versions of the requirements will still be editable, and you will remain editable. You’ll also be able to create a new baseline with live requirements, that will include the modifications madenew baselines at any point, which will include any updates or additions made to the live requirements.
Example: All my When creating the baseline for Release 1 of your product, all Business Requirements (
BR%)are frozen when making the Release 1 of my product, there are 50 requirements. I will be able to continue editing those requirements, and create new Business Requirements in the Confluence page (10 created). When I will make a new —say, 50 in total—are frozen in that baseline. You can still edit those requirements in the live document and add new ones (e.g., 10 additional BRs). When you later create a baseline for Release 2, it will have include the updated total of 60 business requirements. It won’t be possible to edit the requirement’s content in the Baseline ‘Release 1’ because the information is frozen and locked.
...
Note that the content within the 'Release 1' baseline cannot be changed, as it is locked to preserve its original state.
The only exception is External Properties: these can optionally be made editable within a baseline. RY Champions can enable this feature to allow users to add or modify external properties associated with baselined requirements.
To delete 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.