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".
Quick reminder:
Each baseline belongs to a variant, you will be able to freeze requirements in each variant. By default, you may only have one variant called ‘Current’, if you are wondering what is the Variant feature, check out this documentation.
Navigate to the tab ‘Baselines’
Find the variant to freeze requirements, click on ‘Create Baseline’
Enter a name, and a description.
Wait for your requirements to be frozen.
You can edit the name and the description of a Baseline by clicking on the edit button.
The content of a baseline, specifically the requirements it includes, will be locked and uneditable once captured. These requirements are effectively "frozen in time". However, the living (non-baselined) versions of the requirements will remain editable. You’ll also be able to create new baselines at any point, which will include any updates or additions made to the live requirements.
Example: When creating the baseline for Release 1 of your product, all Business Requirements (BR%)—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 include the updated total of 60 business requirements. 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.
You can delete a Baseline by clicking on the 🗑️ icon. Only space administrators and RY champions can perform that action.
To see requirements in a baseline, there are a couple of ways:
In the baseline tab, click on the baseline name, you will be redirected to the search with the correct syntax.
In the Search and Traceability you can use the version dropdown and select a baseline in the list. You can also type the name directly.
You can also use the specific syntax: baseline = 'baseline name’. 💡You can check the search syntax documentation for more information.
In the requirement’s detail, in the breadcrumb at the top of the requirement, you will be able to use the Version dropdown and see the requirement in a given baseline or variant.
When freezing a requirement, it will take a snapshot of the requirement’s detail. Here is the list of all information frozen:
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)
Create and edit a baseline: Users who have edit permissions on the space.
Delete baseline: RY champion and space administrators.
How to check the difference between one baseline and current requirements?
Can I link requirements or Jira issues to a specific baseline?
How can I export my baselines?
Can I import baselines from DC to the Cloud?