Created By  inflectra.elise Wednesday, February 28, 2018

By default, all projects are completely self-contained; artifacts in one project can only be linked or associated with artifacts in the same project.  However, there is a way for the project admin to selectively allow other projects to access artifacts in the current project.  (Administration -> Project Associations)

The cross-project functionality is being introduced gradually.  As of Spira version 5.4, it applies only to requirements, test cases, and incidents.

This article explains how and where the artifacts from another project can be used.

Background

First, say that the project administrator of Project A has set up a project association with Project B and shared its requirements, test cases, and incidents.

Next, say that you are currently working in Project B. 

Association Types Available

You can create the following types of associations in Project B:

  • Test Cases can be associated with the following artifacts in Project A

    • Requirements

  • Requirements can be associated with the following artifacts in Project A

    • Test Cases

    • Requirements

    • Incidents

  • Incidents can be associated with the following artifacts in Project A

    •  Requirements

    • Incidents

Requirements List Page

In addition, on the requirement list page in Project B, you can select "All Projects" in the upper right. 

Then the list will display the requirements from both Project A and Project B.

Article Info
  • Last Updated: 2/28/2018
  • Article ID: KB329
  • Views: 620