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

[Tyler.Burnett]

I'm trying to synchronise two fields in Jira automation via advanced edit. (I cannot use normal issue edit rules, the field is not avaliable) 

via this piece of JSON:

{
"fields": {
"customfield_11487": "{{issue.customfield_11588.asNumber}}"
}
}

 Every attempt and combination I've made always results in this error :
(Specify a number for the custom field (below 100,000,000,000,000) (customfield_11487))

Before anyone asks very obvious question, yes both fields contain numbers/decimal numbers.

Can someone help me understand why this isn't working? Thanks

[Mike Savvin]

You shouldn`t use  "" 

Try

{
"fields": {
"customfield_11487": {{issue.customfield_11588.asNumber}}
}

[Finn Merlett]

This fixed it for me! You don't have to use the customfield identifier either, using the actual name works fine. It's removing the quotation marks that is the key

[Vish]

What Mike mentioned helped me out. But, if you are creating an issue via an API webhook from another platform and encountering the same issue, my answer here might help.

To make it work with a webhook, use the following expression in Jira additional fields:

"Story point estimate": {{webhookData.Story_points}}

Make sure the story_points is an integer when sent via API. Of course, follow the header format provided in the Atlassian documentation of webhook.

[David Ashlock]

@Tyler.Burnett did you ever get this resolved?  I have the exact same issue....

[Finn Merlett]

Try Mike's answer, that was the issue for me

[Nic Brough -Adaptavist-]

What type of field is 11588 ?

[Tyler.Burnett]

Good morning,

Both fields are of the same data type, I've illustrated the two fields down below.

The reason I'm doing this is because backbone refuses to sync to the 'Story Point Estimate' field, so I'm working around it via automation.

[Nic Brough -Adaptavist-]

They are not the same "type" of field, both of them are their own type.

However, you might be able to make their data compatible by dumping the ".asNumber" function, that might be breaking it.