Baseline export

Hi Brendan

As you suggested, the baseline is simply a label pointing to a specific point in the change history. It is a good way to see the aggregate changes between two baselines.

If you want to get a snapshot of the system so that you can see all the artifacts in a specific state (and their relationships), I would recommend using the Product Clone option. This would allow you to create complete clones of the entire projects, including all attachments. This could be then be used for audit purposes. You can make the clones inactive until they are needed.

Regards

David

In SpiraTeam, a baseline is essentially a label pointing to a specific point in the change history, not a full snapshot export of all artifacts. By default, baselines show the differences since the last baseline, but you can retrieve the full state of requirements or artifacts at the time of a baseline using the reporting tools or the Import/Export API rather than relying on the baseline view alone. 

baseline mainly tracks changes between snapshots, not a full frozen copy of every artifact by default. However, you can still get the full state at a point in time it just isn’t exposed as a single “baseline export” button. For audit purposes, the usual approach is to reconstruct the state at the baseline date rather than export the baseline itself. You can do this by running reports (or using the API) filtered by the baseline timestamp—for example, pulling all requirements “as of” that date using version history. SpiraTeam keeps artifact versioning, so each requirement/test case/etc. can be viewed at its historical version corresponding to when the baseline was created.

You’re correct in your understanding: a baseline typically stores a snapshot reference, not just a list of changes. While it can be interpreted as “changes since the last baseline,” most modern tools actually preserve enough version metadata to reconstruct the full state of all artifacts at that point in time.