Dear Community,
I am trying to create a Jira automation which is triggered by the change in the field called fixversions. I want to capture the value of the fixversion value before the change and after the change using the smart values. Below is the code i am using but is doesn't give any out put.
{{fieldChange.fromString}}
{{fieldChange.toString}}
Hi @Surya Narayanan -- Welcome to the Atlassian Community!
You may try using the {{changelog}} or {{fieldChange}} smart values with the syntaxes noted in the documentation, however that may not be accurate.
There is a known defect that list fields like Fix Version do not accurately track the changelog when there are multiple changes to the field over time. This is worsened because some paths to add / change Fix Version apparently do not appear in the history. Please watch / vote for this defect to see progress on the symptom: https://jira.atlassian.com/browse/JRACLOUD-80486
If you still want to try the changelog, please review this documentation for the correct syntax:
Kind regards,
Bill
Hello @Surya Narayanan and welcome to the community :)
To get the value of the old fix version, do you use a variable? And the smart value used in your automation is {{issue.fixVersion.fromString}}
?
Maybe your error was writing {{fieldChange.fromString}}
like in the documentation, instead of {{fixVersion.fromString}}
...
If that's not the case, can you send me a screenshot of your automation?
Hope this helps,
Cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Surya Narayanan
I seem correct the smart value, can you share the setting of your automation and last audit log ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.