Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

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

Chris Vernon October 19, 2025

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.

workflow.png

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.

error.png

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

1 answer

1 accepted

4 votes
Answer accepted
Gor Greyan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 19, 2025

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

dueee.png

Chris Vernon October 19, 2025

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

workflow 2.pngerror 2.png

Gor Greyan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 19, 2025

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 October 19, 2025

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

error 3.pngworkflow 3.png

Gor Greyan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 19, 2025

@Chris Vernon

Thanks for the information.

Let's do that by creating a variable.

Befor the branch, put

Create variable: 

  • Name: oldGoLive

  • Smart value:

     {{fieldChange.from}}
Then, inside the branch, edit the field and set {{var.oldGoLive}}.


 

Chris Vernon October 19, 2025

That worked @Gor Greyan! I had to drop the var. from the edit action, but otherwise that did the trick.

I appreciate your help!

success.png

Like John Funk likes this
Gor Greyan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 19, 2025

Dear @Chris Vernon

Glad that it works.

Also, please accept the answer :)

Have a good day, Chris!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events