I want to prevent users from editing a field (Customer desired Go Live) on standard issues under an epic. To do that, I'm using the log audit to capture the change and then setting the field back to the prior value. I am consistently getting this date format mismatch error. I've tried a number of variations to the fieldChange including * {{fieldChange.fromString.toDate.format("yyyy-MM-dd")}} * {{fieldChange.fromString.toDate("yyyy-MM-dd")}} * {{fieldChange.from.toDate("yyyy-MM-dd")}} but they are all failing - sometimes because nothing is written to the audit and, in the case of {{fieldChange.fromString.toDate.format("yyyy-MM-dd")}} the date isn't getting transformed. I've tried reviewing a number of posts and the Atlassian documentation without success. Thanks for your help. * Atlassian docs 1 * Atlassian docs 2 * Community post 1 * Community post 2

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

Automation - date format error when using logged date to populate custom field

Chris Vernon_gy1cmr

I want to prevent users from editing a field (Customer desired Go Live) on standard issues under an epic. To do that, I'm using the log audit to capture the change and then setting the field back to the prior value.

I am consistently getting this date format mismatch error. I've tried a number of variations to the fieldChange including

{{fieldChange.fromString.toDate.format("yyyy-MM-dd")}}
{{fieldChange.fromString.toDate("yyyy-MM-dd")}}
{{fieldChange.from.toDate("yyyy-MM-dd")}}

but they are all failing - sometimes because nothing is written to the audit and, in the case of {{fieldChange.fromString.toDate.format("yyyy-MM-dd")}} the date isn't getting transformed.

I've tried reviewing a number of posts and the Atlassian documentation without success. Thanks for your help.

Accepted answers

Gor Greyan

Hi @Chris Vernon

Welcome to the Atlassian Community!

There is no need to format the field.

Use the following smart value, which already returns the raw ISO date (yyyy-MM-dd) that Jira expects.

{{fieldChange.from}}

All comments

Gor Greyan

Chris Vernon_gy1cmr

@Gor Greyan thanks for the quick response. I tried that but it also failed.

workflow 2.png error 2.png

Gor Greyan

Hey @Chris Vernon

Got it, the log confirms the smart values resolve correctly, so the issue is likely that the automation is editing a related issue rather than the trigger issue.
When you use a “Branch rule / related work items,” the smart value {{fieldChange.from}} may no longer exist in that scope.

Try this one:
{{triggerIssue.fieldChange.from}}

Chris Vernon_gy1cmr

Still no joy @Gor GreyanThat smart field seems to not have resolved - no values in the audit.

error 3.png workflow 3.png

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

cloud-automation