Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

JSD create API not adding approver

Here is the JSON I am using:

{   "serviceDeskId":"7",
   "requestFieldValues":{      "customfield_15846":{         "value":"CDN Services",
         "child":{            "value":"New Configuration"
      "customfield_15607":{         "value":"High"
      "customfield_15795":[         {            "name":"5badbe291fa6b77b16764f29"
      "summary":"Ticket with attachment",
      "description":"Ticket with attachment"


The approver is not set even when I am sending it - customfield_15795
Can you let me know if I am doing something wrong?

@Angélica Luz


1 answer

0 votes
Angélica Luz
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 03, 2020

Hello Ankit,

Thank you for reaching out to Community!

I tested the same REST API I posted on this other thread just to make sure it was still valid and it worked. 

I see that you are not using the same order, so I'm not sure if it will work. 

Can you please use the same template I posted and just change the IDs?

I see that you have other custom fields, but use that simple one just to check if the approver will be added.

curl --request POST \
--url '' \
--user '' \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--data '{
"serviceDeskId": "12",
"requestTypeId": "223",
"requestFieldValues": {
"summary": "Request JSD help via REST",
"description": "I need a new *mouse* for my Mac",
"customfield_10100": [{ "name":"1a23b45cde67f89g1h23ij4k" }]


@Angélica LuzMy guess is that you are not a programmer? In a JSON, the sequence of key-value pairs (the ones inside the curly brackets {}) doesn't matter. In fact, it doesn't matter in any programming language.


If you use a programming language to call this API, the JSON that is created will have the key-value pairs in any order. Only in an array (the ones with square brackets) can you control the ordering.


Anyhow, just in case I might be missing something, I did try what you said and used this:

curl --request POST \
--url '' \
--user 'email_id:token' \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--data '{
"serviceDeskId": "7",
"requestTypeId": "127",
"requestFieldValues": {
"summary": "Request JSD help via REST",
"description": "I need a new *mouse* for my Mac",
"customfield_15795": [{ "name":"5badbe291fa6b77b16764f29" }]

Still, the approvers were not added. Can it be due to something in the workflow? Any suggestions where I can investigate are welcome

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events