Forums

Articles
Create
cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 

JSON in Create New Work Item Automation

Richard Davis
Contributor
June 18, 2026

Hi,

I am trying to set up an automation (manually triggered) to create a new work item from an existing call. 

This works for the basic fields, and copies the values across as expected, but the Service field (customfield_10075) is not available - I am therefore trying to add it as a JSON additional field, but can't get it working.

The JSON I have is:

{
"fields": {
"customfield_10075": "{{issue.customfield_10075}}"
}
}

but this returns error:

 

Unable to create issue
Can not instantiate value of type [simple type, class com.atlassian.jira.issue.fields.rest.json.beans.CustomFieldOptionJsonBean] from JSON String; no single-String constructor/factory method (customfield_10075)
I have also tried with issue.customfield_10075.value, but this errors in the same way.
Is what I am trying possible, and if so is it just a silly issue with my JSON? 
Thanks in advance!
  Richard 

2 answers

1 accepted

0 votes
Answer accepted
Arkadiusz Wroblewski
Community Champion
June 18, 2026

Hello @Richard Davis 

What specific field type is customfield_10075?

Is the Service field explicitly added to the creation screen for the target project and issue type?

Best,

Arkadiusz 🤠

Richard Davis
Contributor
June 18, 2026

Hi,

It's a cascading select list. It is explicitly added to the create and edit work item screens, which I think is what should be used (as the Create Work Item automation doesn't allow a request type to be specified), although it's also present for the only request type create screen that is set up for this work item.

Thanks,

Richard

Richard Davis
Contributor
June 18, 2026

I've had more of a play and found that this partially works:

{
"fields": {
"customfield_10075": {"id" : "{{issue.customfield_10075.id}}"}
}
}

 

However, it only populates the top level of the field, not the second level!

Arkadiusz Wroblewski
Community Champion
June 18, 2026

Try that

{
"fields": {
"customfield_10075": {
"id": "{{issue.customfield_10075.id}}",
"child": {
"id": "{{issue.customfield_10075.child.id}}"
}
}
}
}

Richard Davis
Contributor
June 18, 2026

Spot on - thanks for all the help!

Like • Arkadiusz Wroblewski likes this
Arkadiusz Wroblewski
Community Champion
June 18, 2026

Glad it helped.

For a cascading select list, your JSON structure must explicitly include both the parent and child nodes, otherwise only the first level populates. That was a Problem.

Your primary problem was related that to this Specific field Type, Jira Expecting object and not plain string.

That only for clarification. Have a great Day😊

Best,

Arkadiusz🤠

0 votes
Richard Davis
Contributor
June 18, 2026

Jira Workflow.jpg

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin Site Admin
TAGS
AUG Leaders

Atlassian Community Events