Share issues between projects

Tricentis Test Management for Jira allows you to share certain issues between projects, optimizing your testing process. If you work in multiple projects, you have the flexibility to link requirement and defect issues from different projects.

Use this feature if you store your requirements, defects, and test cases in separate projects. Alternatively, you can use this feature if you have defects or requirements that apply to test cases in a different project.

Share requirements

Once you have a test case, you can link it to a requirement in any project you have access to. Or, you can turn any issue into a requirement for a test case in another project. Then, the requirement is visible in both projects.

For example, if you create a requirement in project A and link it into a test case in project B, you'll be able to view the requirement in both project A and project B.

You have two options to link requirements from a different project:

  • Open the requirement you want to add a test case to and select Covered by to link a Jira issue to a requirement. Use this option to add a test case from a different project to your requirement.

  • Select Add existing issue as requirement to assign any issue as a requirement for a test case. Use this option to add an issue from a different project as a requirement your test case.

Share defects

You can also create and link defects from a separate project to your test runs.

To link a Defect from a different project, go to the test run you want and select Add existing defect. Then, search for the defect you want by ID or name. The search results include defects from all projects you have access to.

Shared issues in the traceability matrix

For those using multiple projects, the Traceability matrix can also track issues attached to requirements and defects from separate projects.

If you link a test case from one project to a requirement or defect issue from a different project, the attached issue displays in the second project's Traceability matrix with its original project ID. However, the test case the requirement is attached to only displays in the Traceability matrix from it's original project.

For example, if you attach a requirement from project A to a test case in project B, the Traceability matrix in project A does not display the test case from project B. However, the Traceability matrix in project B displays the test case with the attached requirement from project A.

What's next

Now that you know how to share issues from other projects, consider learning more about how to create test cases.

Alternatively, read more about how to run tests you've created.