Automation rule skips execution when FixVersion is updated after release

[Zack Kev]

I’m seeing something odd with one of my Jira Cloud automation rules.
Whenever an issue’s FixVersion is changed after the version has already been marked as Released, the rule says it ran successfully, but none of the actions actually happen. The same rule works normally when the version is still Unreleased, so the logic itself seems fine.

I’m not sure if Jira treats released versions differently or if there’s a limitation I’m not aware of.
Has anyone else run into this behavior? And is there a reliable way to handle post release FixVersion changes without the rule silently doing nothing?

Any insights would help.

[Bill Sheboy]

Hi @Zack Kev 

To provide more context for your question, please post the following:

• an image of your complete rule in a single image for continuity
• images of any rule actions where you are trying something with the Fix Versions that is not working as expected
• an image of the audit log details showing the rule execution

Until we see those...

Work items can add a released version to the Fix Versions field, although in the UX they are filtered from display and must be typed in to find them.  For an automation rule, the options selected in the action may be preventing changes.

Kind regards,
Bill

[Aron Gombas _Midori_]

@Zack Kev 

To troubleshoot this, I would create a dead-simple rule which:

1. uses the same trigger that your actual rule does
2. contains only a single action that writes to the audit log

Using this, you could verify your hypothesis:

1. If the log message appears then it is proven that your rule was started and the action was executed. (In this case, I'd gradually add the actions that your actual rule contains and see what happens?)
2. If the log doesn't appear, but the audit log says that your rule was executed, then open a ticket for Atlassian, as it is obviously a defect somewhere on their side.