nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JSON in Create New Work Item Automation

Richard Davis_hwztqv

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

Accepted answers

Arkadiusz Wroblewski

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 🤠

All comments

Richard Davis_hwztqv

Jira Workflow.jpg

Arkadiusz Wroblewski

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_hwztqv

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_hwztqv

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

Try that

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management