Automation 'Some Errors'

[Joseph Nicholls]

I have an issue where Jira Automation throws (Randomly) a 'Some Errors' error. 

It normally processes fine, but I do not like to be alerted unless there is a true issue. The errors do not hinder the working of the ticket, but like I said. Failure allerting to be should be a true problem so I like to keep these types of notification to a minimum. 

Here is the JSON used to update the Summary field with the Custom Field that is selected from a Select List (Single choice) 

The list contains the Custom Field that we would like to see in the Summary. 

{{customfield_10164.value}}

customfield_10164 is ACH Request Type and it has a list of 3 Custom Field in a drop down used by a Dynamic Form

Here is the Action detail from the Some Errors in the audit log: 

Error editing issues

ISSD-94281 (You must specify a summary of the issue. (summary))

[John Funk]

Hi Joseph,

Can you share the full automation rule that you have and the audit log with the details of the false error that gets generated? 

[Joseph Nicholls]

[Joseph Nicholls]

I have attached a Successful log and a Some Errors log. 

Please let me know if the automation set up needs to be more granular! 

Thanks! 

[Paul Krueger]

Can you show the details of the summary edit step?

[Joseph Nicholls]

Here is the Edit Issue area that is throwing the "error" 

[John Funk]

Try using {{issue.customfield_10164}} for the Summary field edit. 

[Joseph Nicholls]

I tried that and am still sporadically getting the Some Error as above. 

Same type issue but different CF

[Paul Krueger]

What happens if you do it without refetching the issue? 

[Joseph Nicholls]

I think that I might have found the issue. I think that it does not like the customfield_*

It seems to want the name of the Custom Field. For the example above, customfield_10173, the field name is Deposit Services Request Type. If I change it to {{issue.Deposit Services Request Type}}, it appears to not fail. 

Still working to validate this issue further. 

[John Funk]

That's very strange. I have had the customfield value work before when the name would not. But not vice versa.