Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

...

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

    • Yes. Just 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?