Configuring the Versioning Functionality
To use the new Versioning application, simply activate it at the system and product levels, then go to the SpiraApp settings:
You will need to create a custom property for both requirements and test cases of type Text (plain). You can then choose these custom properties in the two dropdown lists:
You should then enter in the text template that you want to be displayed in this custom property. The special token {version} will be replaced by the numeric version number.
There are also two other settings that will affect both requirements and test cases:
- Whether or not to append the version number to the artifact name (off by default)
- Whether or not to restrict creating new versions by workflow (off by default). When on you can only create a new version when the current workflow allows the Name field to be edited. In other words, when this setting is checked you can not create a new Version if the Name field is disabled.
Once you have completed the setup, you can now use the versioning SpiraApp...
Using the Versioning SpiraApp
Once the app is installed and configured, you will see a new toolbar menu entry that shows the option to Create new version:
When you choose this option, it will update the custom property to show the current version number:
In this example, we have created a Version 1, used Inflectra.ai to rewrite the requirement and then created a new version (Version 2). By clicking on the History tab you can see the change history, including the version number change and also the content changes that belong to the new version:
To learn more about using the new Versioning SpiraApp, please refer to the online documentation.
To download the SpiraApp, please go to the SpiraApp marketplace.