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:
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 š¤
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Try that
{
"fields": {
"customfield_10075": {
"id": "{{issue.customfield_10075.id}}",
"child": {
"id": "{{issue.customfield_10075.child.id}}"
}
}
}
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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š¤
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.