How do I display previous value of Fix versions field via Jira automation?

[Troy]

Hello, I am monitoring the changes to 'Fix versions' field in an issue. The field type is set as multi-select drop-down list.

I am using the Send Email trigger and in my email content I have kept as below

Previous Value: {{fieldChange.fromString}}

Current Value: {{fieldChange.ToString}}

So if I had A currently against Fix versions field and I change it to B then the mail body shows as

Previous value:
Current value: B

The current values displays properly with all my tests but the previous value returns blank.

Please let me know a way to capture and display previous value as well.

[Bill Sheboy]

Hi @Troy 

There are multiple problems, and inconsistent behaviors, for the issue history and list fields like fixVersion, and so you may not be able to do what you ask. 

I have observed Atlassian closing several defects on this symptom, or moving them to the dreaded "Future Consideration" or "Long Term Backlog" statuses.  Here are a couple of examples you may want to watch to see any progress: https://jira.atlassian.com/browse/AUTO-473 and https://jira.atlassian.com/browse/JRACLOUD-75543

And also...as you appear to be the site admin for a paid Jira Cloud license, consider submitting a new defect for this here: https://support.atlassian.com/contact/#/  It is possible they are working on resolving this and the public backlog tickets have not been updated by their product managers.

Kind regards,
Bill

[Troy]

Many thanks for your response, Bill.

I will submit a new defect for this.

One query: if you refer the screenshot, you will notice there are 2 fields with the same name - is one a custom field and the other Jira system field? My rule works partially when I select the one that is green highlighted. I say partially since it fails to populate the previous value. It does not work at all if I select the 2nd Fix versions in the screenshot.

Also could you please check my query here JQL to show all Dependencies linked to mentioned E... (atlassian.com) and suggest any possible solution? Ignore if already seen earlier :) Thanks.

[Bill Sheboy]

When you see two (or more) fields with the same name in that list it is likely there are multiple fields with the same name.  Please review your custom field configuration as having multiple will certainly cause problems.

[Troy]

Thanks Bill.

I assume you have already checked my other query JQL to show all Dependencies linked to mentioned E... (atlassian.com)? :)