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.
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.
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?