This article describes how to retrieve artifact's associations due to the dependency type that become challenging.
Sometimes you may need to get the list of incidents associated with a requirement but that can be challenging in case an implicit association exist.This article can help you to get these associations.
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 6.0, it applies only to requirements, test cases, tasks (SpiraPlan and SpiraTeam), and incidents.
This article explains how and where the artifacts from another project can be used.
Several customers had questions about the "copying of artifacts", specifically looking for information about which linked data and dependent data elements are copied. In this article we clarify this information.