JIRA fix version should not be editable after release

[Alpa Padliya]

Hello all,

I am searching for an automation in JIRA to avoid tagging fix version after release.

For Example my fix version 1.0.0-x is released and after release if anyone is trying to tag the same version (1.0.0-x ) in any ticket for field fixversion then this version should not reflect in the list to tag.

Automation or ay permission restriction would be helpful for that.

Thanks in advance.

Regards

Alpa Padliya

[Walter Buggenhout]

Hi @Alpa Padliya,

The easiest way to achieve this, is to archive your released version. As soon as you do that, it will no longer be available for selection in the fixversion dropdown.

Hope this helps! 

[Alpa Padliya]

Thanks @Walter Buggenhout .. i have already tried this but it will impact for my another field i.e. Affected Version". if i will archive version then version will not reflect in Affected version list also. and it would load my work. :)

[Bill Sheboy]

Hi @Alpa Padliya 

Adding to Walter's answer...

This may not be easily possible to detect/prevent with an automation rule.  The ability to determine the changed values for fixVersion in a rule has stopped working, and you may watch that defect here: https://jira.atlassian.com/browse/JIRAAUTOSERVER-207

A work-around would be a bit complicated, and assumes you have one-and-only-one Fix Version assigned to an issue:

• trigger on change to Fix Version
• using a web request, call the REST API to gather all versions for the project, 
• check if the fix version matches a released one, such as with an advanced branch on released versions or list-parsing and advanced compare with "contains"
  • take some action: email, mention, clear the value, etc.

Kind regards,
Bill