Copying Links from Test Run to Test Cycle May Not Work Externally

Author: Erik Haake
Date: 9/5/2025
Audience: Everyone
Environment: Cloud and Self-Hosted, Replicated KOTS (all versions)

Summary 

On Test Run items, links to the associated Test Plan, Test Cycle, and source Test Case are automatically generated when the Test Run is created. However, these links are not absolute and rely on the docId property for navigation. As a result, copying and sharing these links externally may not direct users to the intended Test Cycle. Instead, the link will always navigate to the most recent Test Cycle.

Example:

• A Test Case contains a link to its source Test Cycle, named First Cycle.

• Clicking the link within Jama navigates correctly to First Cycle.

• Copying the link and opening it in a new tab navigates to the Test Cycle page, but the wrong Test Cycle is selected. It will always default to the latest Test Cycle.

If we click the link, it takes us to the correct Test Cycle. 

However if we copy the link and open it in a new tab, it navigates to the Test Cycle page, but with the wrong Test Cycle selected. Doing so will always navigate to the latest test cycle.

Link comparison:

• Link from Test Run:
  https://ehaake-robotics.jamacloud.com/perspective.req?docId=17137&projectId=58

• Full URL from direct navigation:
  https://ehaake-robotics.jamacloud.com/perspective.req#/testPlans/17136/testCycles/17137/testRuns?projectId=58

Solution 

The automatically generated links on a Test Run depend on the docId property, which does not include the specific Test Cycle information.

Cause 

The links that are automatically generated on a Test Run depend on the docId property which does not contain the specific test cycle information.

Additional Information / Metadata /Resources 

• Keywords: Test Run, Test Cycle, Link, URL

Feedback:
Have suggestions or improvements? Please leave your feedback in the comments section below.