Inconsistent data returned for RM resource in Validated By links content title field based on whether logged in or not to RQM
Environment:
Scenario: 1. Log in to RM application 2. Open a Module 3. Add Validated By column 4. Include links, tags and comments from base artifact
5. Run an RPE report to display the Title of the Validated By links.
6. Verify Data source XML: Put resource in browser to view data: https://servername:port/rm/publish/resources?resourceURI=_xxxxxxxxxxxxxxxxxxx (core id, not id of resource when viewing in Module)
7. LOG INTO RQM 8. Run an RPE report to display the Title of the Validated By links.
9. Verify Data source XML: Put resource in browser to view data: https://servername:port/rm/publish/resources?resourceURI=_xxxxxxxxxxxxxxxxxxx (core id, not id of resource when viewing in Module)
Issue: The XML file for data source (https://servername:port/rm/publish/resources?resourceURI=_xxxxxxxxxxxxxxxxxxx) displays different results for Validated By links of a resource based on whether user is logged into RQM or not. This results in inconsistencies in report output based on whether user is logged into both applications (RM & RQM) or not when running the report on the RM application. Not sure how to resolve this issue and allow the report to be run on RM application and show the correct data (BOTH links). I would think BOTH the test script [step] title AND the test case title (since both appear to be linked in the Validated By links) should be available in the XML for the data source on the DNG side without having to go to RQM to report on this information. Any assistance to get correct title information from DNG-side for BOTH links in the data returned from the resource. Also posted on RPE Devworks forum: https://www.ibm.com/developerworks/community/forums/html/topic?id=2b0ddf88-b0eb-4bd3-b7c0-75ec59838c4b&ps=25
|
One answer
|
Refer to article at: https://jazz.net/library/article/1241. I no longer get the TC title info that is stored on the DNG side, I traverse the OSLC link stored in the relation field in DNG via the OSLC schema and then go to the REST API. It was the OSLC schema hop that was missing.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
Out of curiosity, how can you link a test script to a requirement artifact? Also, the data source the you verified should not be any different to what you saw in RPE. You may try to check the OSLC presentation of the requirement artifact using a OSLC/REST client, and you should see two "nodes" there.
https://servername:port/rm/resources/_xxxxxxxxxxxxxxxxxxx
See the below article for more details.
https://jazz.net/library/article/1197
"...how can you link a test script to a requirement artifact?" Requirements were linked to a Test Script Step in RQM and in DNG is illustrated by the "757: New Requirement [3]". When a user hovers over the link it says it is of type test script.