Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 4 Next »

Use case

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:

Diff History Baselines Variants.png

How to create a Baseline ?

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.

To freeze all requirements in a variant

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

To edit a baseline

You can edit the name and the description of a Baseline by clicking on the edit button.

The content of the baseline (the requirements) will not be editable, the requirements will be captured and frozen in time. The living requirements will still be editable, and you will be able to create a new baseline with live requirements, that will include the modifications made.

  • Example: All my 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 baseline for Release 2, it will have 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.

The only information that could be modified in the baseline of a requirement will be External Properties. This is an optional feature, RY Champions can make that available to their users so they can add external properties on baselined requirements.

To delete a baseline

You can delete a Baseline by clicking on the 🗑️ icon. Only space administrators and RY champions can perform that action.

How can I see requirements in my Baselines ?

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.

What information of the requirement is frozen in a baseline?

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

Permissions

  • Create and edit a baseline: Users who have edit permissions on the space.

  • Delete baseline: RY champion and space administrators.

Frequently asked questions

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

  • No labels