ClearQuest - How to remove ADT Defect children using REST APIs
Uday Bhosale (13●4●8)
| asked Apr 27 '15, 3:26 a.m.
edited Apr 28 '15, 8:35 a.m. by Krzysztof Kaźmierczyk (7.4k●3●75●103)
We are developing a .Net Application which uses ClearQuest as defect management tool. We are however stucked in at a point where we need to delink a defect using CQs REST APIs
We are able to add child defect in an existing defect/new defect. Now what we need to do is remove the child ADT defect from a defect. How to do this using REST API? Can anyone help us getting the solution for this?
|
3 answers
Indeed you should post the question in the developerWorks CQ forum. There are users in the CQ forum did this before.
https://www.ibm.com/developerworks/community/forums/html/topic?id=37ea1ba7-a504-4d79-960e-a76a2eac0d35
It depends on whether you have child defect or defects linked to the parent. Precisely, whether the field is a Reference field, or Reference List field. For a Reference field, you should just do a full or partial update on the parent defect. For a Reference List field, you need to update the field directly.
For example, using the SAMPL sample database, when you GET a defect, you should see the below entry - this is a Reference List field linked to the Customer record type.
<customer oslc_cm:collref="http://win08rcc8/cqweb/oslc/repo/8.0.0/db/SAMPL/record/16777224-33554433/field/customer"/ >Do a GET following the link to the field and you should get an XML presentation of the field values. Then remove the member(s) in the presentation and PUT the modified XML back to the same URL. If successful, you should get an HTTP 200 code. |
Hi Uday,
This is CLM applications forum. You should ask this question on CQ forum (or stackoverlflow). |
Uday,
You will have to get the id of the child Record and perform the action delete over the child record. so you should do a query of all child and identify which one you want to remove, or remove the link only.
|
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.