Access the latest added version added to an issue via smart value

[yaron]

Hello,
I have a case where I need to save the latest version added\ removed rom the multi select fixVersion field.
My problem - I can't find a way to access via smart value the latest added release to the fixVerison field.
{{issue.fixVersions.name}} - returns all the versions mapped to the issue orders by the version id. 

[Inactive Stephen]

I found this question whilst also trying to find this answer.

I found this article on fieldchange useful - https://confluence.atlassian.com/automationkb/capturing-added-and-removed-values-from-multi-picker-field-in-jira-cloud-automation-rules-1252330496.html

Ste

[Bill Sheboy]

Hi @yaron 

Please take a look at the {{fieldChange}} and {{changelog}} smart values to do that: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/

Kind regards,
Bill

[yaron]

Hi @Bill Sheboy -
Thanks for the advice but field.Change and changelog are not supporting list fields:
https://jira.atlassian.com/browse/JIRAAUTOSERVER-207

[Bill Sheboy]

Thanks @yaron 

I recall this did work in the past as I have an example rule that previously worked for this (early last year, I believe).

Further testing shows this to be quite "wonky", as the {{toString}} does work only when you add a new version as part of the issue's field edit!  I noted that in the defect to give the devs something to ponder.

[yaron]

{{#changelog.Fix Version}}{{fromString}}{{/}} -

• Add version - return empty.
• Delete version - return name of the latest deleted version from the ticket.

{{#changelog.Fix Version}}{{toString}}{{/}}

• Delete version - return empty.
• Add version - return name of the latest added version to the ticket.

[Bill Sheboy]

The smart value for that field is fixVersion or "Fix versions".  Smart values are name, spacing, and case-sensitive.

[Jack Brickey]

Hi @yaron ,

I just setup the below automation and it successfully captured the most recent Fix version.

The smart value text is...

{{issue.fixVersions.name}}

[Jack Brickey]

Here is a screenshot where the comment action correctly shows only the latest version.

[yaron]

Hi @Jack Brickey 
Please note it printed both versions, not only the latest one added (this is my problem):

[Jack Brickey]

Lol...you are correct. I totally missed that. 😖

[Jack Brickey]

Try this...

{{issue.fixVersions.last.name}}

[yaron]

last return the latest version in the field based on the release id and not based on the latest added.

[Jack Brickey]

Yes I see, the FV field reorders the entries automatically which results in the latest always being last. 🫤