This page is maintained for older versions of Spira only. The latest documentation can be found at: https://spiradoc.inflectra.com

Spira 4.2 User Manual Help Viewer

1. Introduction
2. Functionality Overview
3. User/Project Management
4. Requirements Management
5. Test Case Management
6. Incident Tracking
7. Release Management
8. Task Tracking
9. Resource Tracking
10. Document Management
11. Reports Center
12. Source Code
13. Planning Board
14. Mobile Access
Search:
1. Introduction
2. Functionality Overview
3. User/Project Management
4. Requirements Management
5. Test Case Management
6. Incident Tracking
7. Release Management
8. Task Tracking
9. Resource Tracking
10. Document Management
11. Reports Center
12. Source Code
13. Planning Board
14. Mobile Access

6.2.7. Associations

In this tab, the main pane displays a list of any requirements, tasks, test runs, test steps or other incidents that are associated with this incident:

The incidents and tasks in this list are ones that a user has decided are relevant to the current one and has created a direct link between them. In the case of requirements and test cases, the association can be either due to the creator of an incident directly linking the incident to the requirement or test step, or it can be the result of a tester executing a test-run and creating an incident during the test run. In this latter case, the check-box to the left of the association will be unavailable as the link is not editable.

Each association is displayed with the type of association (related-to, vs. a dependency), name of the artifact being linked-to, type of artifact (requirement, incident, etc.), the name of the person who created the association, and a comment that describes why the association was made. In the case of an indirect association due to a test run, the comment will contain the name of the test run.

In addition, when using SpiraPlan or SpiraTeam, you can select the checkbox marked “Include Source Code Revisions” and the system will also scan the source code repository for any revisions that are linked to this artifact. Since that can take be slower than accessing SpiraTeam, it is provided as an option that you can enable and disable:

You can perform the following actions on an association from this screen:

  • Delete – removes the selected association to the other artifact. This will only delete the association, not the linked artifact itself.
  • Refresh – updates the list of associations from the server, useful if other people are adding associations to this incident at the same time.
  • Apply Filter – Applies the entries in the filter boxes to the list of associations
  • Clear Filters – Clears the current filter, so that all associations for the current incident are shown.
  • Edit – Clicking the [Edit] button to the right of the associations allows you to edit the association type and comment fields inline directly on this screen.

To create a new association, simply click the <Add> hyperlink which will display the “Add New Association” popup dialog box:

Once you have selected the appropriate artifact type, you will then be able to choose the specific artifact you want to link to. In all cases, you can choose the item from a scrolling selection box, or you can either enter the ID of the artifact directly (if known). In either case you can also add a comment that explains the rationale for the association. If you’re adding an association to a test step, then there are actually two selection boxes, one to choose the overall test case and the other to choose the specific test step.