Automation for Fixversion update

[Prahlad Rebala]

I am trying to create an automation based on changes to fix version of stories

whenever fix version of story is changed, I want the epic to have the latest fix version in all of the stories. 

Trigger : Fix version change

condition 1: Issue type is User story

condition 2: {{fieldChange.to}} is greater than {{fieldChange.from}}

Action : 

For parent Epic

set Fix versions to {{fieldChange.to}}

Somehow, the fix version is getting set in the epic irrespective of the value. 

Please note that our fix versions are something like

2.1,

2.2,

2.3,

2.4 and so on . In JQL when i check for fixVersion>"2.3" , all issues corresponding to later releases are shown but however my. comparison in the automation condition (condition2)  isnt working. 

Is there a suggested way for comparing fix versions in an automation? 

Appreciate your help/suggestion

[Riley Venable]

The comparison operators (e.g. ">") use the version order that has been set up by the project administrator, not a numeric or alphabetic order. It is suggested to use the FixVersion operator in JQL to search for a version's issues and to search by version ID rather than by version name in order to avoid issues from multiple projects. It is also recommended to use the latestReleasedVersion() and earliestUnreleasedVersion() functions when searching for issues with a Fix Version of a specific version. As for the automation issue, it is unclear what the problem is and further information is needed to provide a solution.

[Prahlad Rebala]

Hi Riley 

Thanks for your input.

My goal for the automation is to ensure that

When a story's fix version is changed (we just have one fix version assigned to a story), the automation should ensure the latest fix version is updated for the Epic. 

i.e. my stories may be spread across multiple fix versions. When I update my stories based on when they will be released, I would want the epic to reflect the latest(last FixVersion of the stories) 

Appreciate if you can recommend the best possible way to achieve this

[Riley Venable]

One possible solution to achieve this automation is to create a new automation rule in your service project. You can set the trigger to "When an issue is updated" and add a condition to check if the issue type is "Story" and if the fix version field has been changed. Then, you can add an action to update the fix version field of the linked Epic to the latest fix version of all linked stories. This way, whenever a story's fix version is changed, the automation will update the Epic's fix version to the latest one. You can customize this rule further to suit your specific needs.

[Prahlad Rebala]

Hi Riley, 

Yes thats my goal and I have all the conditions matching what you mentioned but how do I go about this step: (I mean this is where I was struggling and ended up adding anther compare condition) 

"Then, you can add an action to update the fix version field of the linked Epic to the latest fix version of all linked stories. "

[Prahlad Rebala]

 Addendum: 

 I have realised that my {{fieldChange.from}} value when I change fixversion is always coming up as null and thats is  the reason why my comparisons are failing. I am not sure why thats the case