Automation - Trigger condition when the fixversion is changed and was version X.XX.X

[Chad Bellan]

With the automation, I want to receive a slack message after the fixVersion was changed from the version that I'm tracking (X.XX.X).  

I can trigger the condition when it equals XX.XX but not when it's changed from X.XX.X to Y.YY.Y

[Bill Sheboy]

Hi @Chad Bellan 

For a question like this, context is important for the community to help.  Please post the following:

• what type of project is this (e.g., company-managed, team-managed, etc.), 
• an image of your complete automation rule,
• images of any relevant actions / conditions / branches,
• an image of the audit log details showing the rule execution, and
• explain what is not working as expected.

Until we see those...

If your rule is triggered on a change to the Fix Versions field, you could try using the changelog smart values to detect what you describe:

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--changelog--

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--fieldChange--

However, please note well: when a field like Fix Versions is changed too many times, the changelog no longer works correctly when passed to rule triggers.  This is a known problem with list fields (e.g., Fix Versions, Affects Versions, Sprint, etc.)  The only workarounds for that are to manually track changes with additional custom fields and to calculate the differences.

Kind regards,
Bill

[Toby Moore]

I think the problem you're going to have is that the trigger is normally when the issue is changed, so you would probably need to look into smart values to try and get the old fixVersion, or look at triggering a version change by some other action.