Error while parsing additional fields;while using the more options feature in automation

[Amer Jneid]

I had an error while parsing each time the rule executes

"fields": {"update": {
"customfield_10023": "{{triggerIssue.customfield_10023}}",
}
}

[Bill Sheboy · Accepted solution]

Hi @Amer Jneid 

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected.  Those will provide context for the community to offer ideas.  Thanks!

Until we see those...

What is the type of your custom field?  The type of the field impacts the format used when making updates with JSON edits: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/

Kind regards,
Bill

[Amer Jneid]

The rule compares the Epic and stories' Target End (a custom date field 'cf-10023') and updates the parent Epic if the story target end is greater. The challenge is that Jira automation does not support this field; I attempted to update first a supported field and use the "more options" to update the unsupported customfield_10023 which is a date type.

[Bill Sheboy]

Thanks for that information.

There are some missing curly brackets in your JSON, an extra comma, and the date is in the incorrect format.  To set that field it must be in jiraDate format: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Date-picker-custom-field

{
  "fields": {
    "customfield_10023": "{{triggerIssue.customfield_10023.jiraDate}}"
  }
}

Also note: there is an error in your update of the Due Date field: there are two periods after triggerIssue in the smart value expression.

[Amer Jneid]

Thank you so much, it solved the JSON message error but it created another error.

[Bill Sheboy]

Would you please post an image of your current complete rule and of the edit issue action?  The format jiraDate should match what the error shows:

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-format---

UPDATE:

I forgot that because the Advanced Roadmap fields are not fully supported by rules yet, they appear as text to the rule, not as a date type.  And so they must be converted first:

{
  "fields": {
    "customfield_10023": "{{triggerIssue.customfield_10023.toDate.jiraDate}}"
  }
}

[Amer Jneid]

I removed the .jiradate and it worked perfectly thank you so much

{
  "fields": {
    "customfield_10023": "{{triggerIssue.customfield_10023}}"
  }
}