Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Link Requirement artefact to test Step through RQM REST API

Hello,

I'm trying to create a python code to create ELM 7.0.2's data through the different types of artefacts and I'm strugling to create a visible link in the UI using the REST API.

Information:
I'm using a Bulk upload of a bunch of test script simustaneously
I've tried those elements (inside ns2:testscript/ns2:steps/ns8:step with ns2 as "http://jazz.net/xmlns/alm/qm/v0.1/" and ns8 as "http://jazz.net/xmlns/alm/qm/v0.1/testscript/v0.1/"):
  • rdf:Description/ns11:validatesRequirement/rdf:resource (with ns11:"http://open-services.net/ns/qm#")
  • ns8:attachmentlinks#href
  • ns11:validatesRequirement#href
  • ns8:requirement
I got the same issue using RQM Excel Importer with LinkByExistingID(M) (with id number like "6585") or with LinkExisting(M) (with <server>/rm/resources/<url>)

(My request header contains oslc_config.context)

Thanks in advance for your help

0 votes


Accepted answer

Permanent link
I found the solution:

The reportable REST API as Requirement as read-only value due to his necessity (as in the UI) to be part of a configuration.

To add it, you must use OSLC query which use versionedTestScript Artefact and ExecutionElement2 (for versioned step).

Library that can help you find what you need:

Hope those element help other in struggle

Ralph Schoon selected this answer as the correct answer

0 votes

Comments

Thanks for sharing Lucas! 

1 vote

Your answer

Register or log in to post 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 12

Question asked: Mar 08 '22, 6:04 a.m.

Question was seen: 813 times

Last updated: Mar 17 '22, 5:36 a.m.

Confirmation Cancel Confirm