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
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.
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}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@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}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That worked @Gor Greyan! I had to drop the var. from the edit action, but otherwise that did the trick.
I appreciate your help!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear @Chris Vernon
Glad that it works.
Also, please accept the answer :)
Have a good day, Chris!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.