Validated By link from DOORS Next artifact to ETM test case is not visible in DOORS Next

Created by Piotr Anioła on Sun, 07/18/2021 - 03:32

Published URL:

https://www.ibm.com/support/pages/node/6473369

6473369

Troubleshooting

Problem

Validated By link from IBM DOORS Next Generation (DNG) artifact to an IBM Engineering Test Management (ETM) test case is not visible in the DOORS Next.

Symptom

The link from the ETM test case to the DNG artifact exists.

When you click the link, the DNG artifact loads, but it does not contain the link back to the test case.

Cause

Unknown.

Environment

Global configuration-enabled project areas in ETM and DNG.

Diagnosing The Problem

Updating the test case causes the link to the test case to appear in the DOORS Next artifact links.

Resolving The Problem

It is not possible to find the cause of existing occurrences.

To troubleshoot new occurrences,

First, check that the Link Index Service (LDX) for the ETM and GC data sources are up-to-date.

If the LDX data sources are up-to-date, then run TRS validation of ETM and GC, from the applications' TRS Diagnostics page.
If resources are added or removed from the TRS, then allow these changes to update in LDX.

If the application data sources are correct, then run LDX validation on the ETM and GC datasources.

If the issue is still not resolved, then enable tracing of the datasource:

Navigate to https://<server:port>/ldx/web/admin/data-sources
Click the ETM Resources datasource
Switch Enable logging of TRS changelogs to Debug

These steps result in logging TRS processing to a separate set of files on the server (not ldx.log or qm.log).

If a new occurrence is spotted, open a new case for IBM Support and provide the following details:

qm.log
ldx.log
TRS change log
TRS Feed
URL of the QM resource
URL of the RM resource
OSLC representation (result of an OSLC GET) of the QM resource.

Internal Use Only

Be careful in using this technote with customers. The first step in troubleshooting link visibility issues would be to 1) validate the LDX datasources in play here, namely the ETM and GC datasources, 2) validate the ETM TRS, 3) validate the GC TRS.

Only once the validation has not resolved the issue, should you proceed to investigate the TRS changelogs.

Open a skill case for L3 and reference case TS005777817

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSUVV6","label":"IBM Engineering Test Management"},"ARM Category":[{"code":"a8m50000000CjGSAA0","label":"Test Management-\u003EIntegrations-\u003EIBM-\u003ERational DOORS Next Generation"}],"ARM Case Number":"TS005741922","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]