How to assign a Insight object to a custom field using Rest API?

Andre Lara Oliveira e Silva_gq3bce

Hey there, 

I just have an issue type that goes with an Insight object under a customfield.

However, i can not manage to create this issues neither using Jira for Python lib or Jira REST API directly.

I went over these two topics below, and none of the solutions worked for me

https://community.atlassian.com/t5/Jira-Service-Management/JSON-body-example-that-links-an-Insight-object-to-a-JSM-issue/qaq-p/1986713

https://community.atlassian.com/t5/Jira-Service-Management/Jira-API-Insight-object-customfield/qaq-p/1276723

 

for the payload as 

{

   "fields": {

      "project":{"key":"DEMO1"},

      "summary": "Create JIssue test",

      "description": "Create Jissue test",

      "issuetype": {

          "id": "10213"

       },

      "customfield_10424" : [{

         "workspaceId":{workspace_id},

         "id":"446",

         "objectId": "446"

       }]

    }

}

i just got a server error

{"errorMessages":["Internal server error"],"errors":{}}

if i replace the insight object formatting, and pass only the key, the ticket is created, but with the customfield as empty.

{

   "fields": {

      "project":{"key":"DEMO1"},

      "summary": "Create JIssue test",

      "description": "Create Jissue test",

      "issuetype": {

          "id": "10213"

       },

      "customfield_10424" : [{

         "key":"CUS-445"

       }]

    }

}

 

This is how a manually issue, with Insight object properly set, looks like for the customfield

 

 

if i just try to update that issue by code, using:

issue.update(fields={'customfield_10424':[{

"key":"CUS-175"

 }]})

 the customfield_10424 will go empty. 

I would be pleased if someone could help me figure this out, or maybe explore other alternatives, Thanks!

Andre Lara Oliveira e Silva_gq3bce

After going deeper on that, just found out the syntax that worked for me.

customfield_10424=[{

"id":"{workspaceId}:445", 

 }]

idk why this is not well document over jira docs, since there are similar scenarios and different syntaxes.