...
If you wish to add additional details, you can click on the Details tab. This will allow you to add all the additional details that you are able to add when creating a script in the Script Library. For an Agile run, this information is optional and the default values for mandatory fields such as Priority, Status and Type will automatically populate these fields.
Agile Run Relationships
Also notice that Agile Runs also have a Relationships tab. Initially no relationships will exist as it is not created from a master script in the Script Library. If an incident is raised during the agile run or if the agile run is later converted to a script in the Script library, relationships will automatically be added.
From the Relationships tab, you can add a relationship from the agile run to a requirement. To do this, click run, then select the Add button on the bottom right side of the screen:
The Add Relationship dialog screen will appear allowing you to create a coverage relationship:
- Source will automatically be populated with the name of the Agile Run.
- Relationship type will automatically populate with Coverage (AgileRun<-> Requirement).
- Destination is the target requirement that this agile run will cover. Select the requirement from the selector.
Direction is the direction of the relationship. This will automatically be populated with Source to Destination. In this instance coverage can only be from the Agile Run to the Requirement. Agile Run is the Source and the Requirement is the Destination.
Converting Agile Runs to Scripts
...
Once you have clicked create, select the package/folder in the script library where the new master script should be created.