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; } } }

Copying custom fields to new ticket via automation

Mark_09sc0z

I realise there are two or three previous threads on this but I've (carefully) applied their advice and it's still not working

I'm automating creating a new ticket when a ticket changes workflow status. I want to copy across a custom field with a numeric value to the new ticket. Here's the code I'm using:

{
"fields": {
"parent": {"id": "28996"},
"customfield_10413":"{{issue.customfield_10413}}"
}
}

(The "parent" setting is irrelevant but included just so you can see the full code)

In the automation logging, I get the following error:

Create issue

Error creating issue

Specify a number for the custom field (below 100,000,000,000,000) (customfield_10413)

In the names page for the ticket, the custom field value appears as follows:

"customfield_10413":4.0

Can anyone advise please?

Accepted answers

Bill Sheboy

Hi @Mark -- Welcome to the Atlassian Community!

Have you tried using this syntax to get the value of the field: {{issue.customfield_10413.value}}

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Mark -- Welcome to the Atlassian Community!

Have you tried using this syntax to get the value of the field: {{issue.customfield_10413.value}}

Kind regards,
Bill

Mark_09sc0z

Hi Bill, thanks for your reply. Tried that a few times yesterday, just tried it again and got the same error message.

Mark_09sc0z

Screenshot 2022-01-21 080542.png Screenshot 2022-01-21 080554.png

Mykenna Cepek

First, confirm that the type of this custom value is indeed numeric.

If so, I suspect the value (to the right of the colon) should not be quoted. See:

https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Using-smart-values

Consider testing this by hardcoding the JSON with a simple number, to see if that works. If it does, then focus on the smart value syntax for the value (without quotes).

"customfield_10413": 4