How to link defects using ZAPI cloud?

Krishna-Kumar.Rajendran July 12, 2020

Hi Team,

I want to link defect through ZAPI cloud. but the request body template provided in https://zfjcloud.docs.apiary.io/#reference/execution/update-execution/update-execution is invalid Json. when i hit endpoint with requestbody by modifying defect entity as json array, i get below error

{    "errorType""ERROR",    "clientMessage""issueId field value is null or 0 is not valid.",    "errorCode"123}

 

But if i remove the defect entity, the status is getting updated successfully. Please help

2 answers

1 accepted

0 votes
Answer accepted
Deleted user January 20, 2021

Request example in docs is incorrect

{"status":{"id":1},"id":"0001456664462103-5a6ee13a3f6b-0001","projectId":10000,"issueId":10000,"cycleId":"0001456664262308-5a6ee13a3f6b-0001","versionId":-1,"comment":"Comment for execution","defects":"["IZ-1","IZ-2"]","assigneeType":"currentUser/assignee","assignee":"userKey"}

defects field should be list of native jira ids. e.g

"defects":[12345,67891]

 not

"defects":["proj-123","proj-345"]
Krishna-Kumar.Rajendran January 20, 2021

So only way to extract the native Jira id in backend is through Jira API alone. not by Zapi!

this has to be addressed whereas we can use Testcase IDs instead of native jira ids for test case add, but not for defect mapping

Like Deleted user likes this
0 votes
Krishna-Kumar.Rajendran September 29, 2020

Can sombody help? It's been open for long time. should i map it to anyone? 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events