Child Artifacts

When you copy an artifact in Spira, the following child artifacts are copied over:

Copied artifact

Test Coverage / Test Case

Tasks

Attachments

Requirement

Test run

Test set

Incidents

Requirement

-

-

-

-

Tasks

-

-

-

-

-

-

Risk

-

-

-

-

-

Test Case

-

-

x

x

x

Test Set

-

-

-

x

-

x

Incident

-

-

-

-

-

-

Release

x

x

x

-

X

x - the associations are not being copied with the artifact copy 

“-” - not relevant for the artifact

- the associations are being copied with the artifact copy 

Associated Artifacts

When you copy an artifact in Spira, the following associated artifacts are copied over (Associations tab):

Copied artifact

Associated Requirement

Associated Task

Associated Risk

Associated Test Case

Associated Test Set

Associated Incident

Associated Test run

Requirement

x

-

x

-

-

x*

-

Tasks

-

x

-

-

-

x

-

Risk

x

-

x**

x

-

x

x

Test Case

-

x

x

-

-

-

-

Test Set

-

-

-

-

-

-

-

Incident

x***

x

x

x

-

x***

x***

Release

-

-

-

-

-

-

-

*If incidents were created in the test cases, which were connected with requirements before the test run in which the incident was created, then the associations with these incidents will be copied by copying of the requirement and cannot be eliminated. All other associations of requirement with incidents are not copied by copying of the requirements

**If risks are being copied from risk, then the original risk is being automatically connected with the risk copy in the associations tab 

***If Incidents are being copied from incidents, then:

  • the original incident is being automatically connected with the incident copy in the tab associations
  • the requirement and the test run, which were connected with the original incident during/before the test run in which the incident was created, stay connected with the copy of the incident and cannot be eliminated