I suspect the reason there is no published solution is because this is extremely complicated to implement correctly. There are many ways the data can be changed, and many places where you need to put triggers to ensure you are displaying current data.
For instance, you of course can't display an associated requirement for a test instance until the test instance is created. So, in the process of creating a test instance you need to catch that action and create custom code to
- trace back to the original test case
- from there figure out the linked Requirement.
To do that requires use of the OTA API within the workflow code. But also consider that there may be more than one linked requirement. And more than one way to create a test instance. You can add a single test to a test set. You can add a whole folder's (or hierarchy of folders) collection of tests to a test set. You can create test instances by copying an existing test set.
Next, consider that the link between a test and a requirement can be severed after the test instance is created. In that case, you need to capture that action and right custom workflow code to
- Find all test instances associated with the test
- remove the Requirement info from the test instance
Next, consider that a link between a test and a requirement can be added after the test instance is created. In that case, you need to capture that action and right custom workflow code to
- Find all test instances associated with the test
- add the Requirement info to the test instances
Next consider that those links can be added/removed when you are in the Test Plan module or the Requirements module. So there are multiple places where you may have to capture the action.
For instance, you of course can't display an associated requirement for a test instance until the test instance is created. So, in the process of creating a test instance you need to catch that action and create custom code to
- trace back to the original test case
- from there figure out the linked Requirement.
To do that requires use of the OTA API within the workflow code. But also consider that there may be more than one linked requirement. And more than one way to create a test instance. You can add a single test to a test set. You can add a whole folder's (or hierarchy of folders) collection of tests to a test set. You can create test instances by copying an existing test set.
Next, consider that the link between a test and a requirement can be severed after the test instance is created. In that case, you need to capture that action and right custom workflow code to
- Find all test instances associated with the test
- remove the Requirement info from the test instance
Next, consider that a link between a test and a requirement can be added after the test instance is created. In that case, you need to capture that action and right custom workflow code to
- Find all test instances associated with the test
- add the Requirement info to the test instances
Next consider that those links can be added/removed when you are in the Test Plan module or the Requirements module. So there are multiple places where you may have to capture the action.