Issue Automation - Update Fix Version based on version naming

[Keary Norcio]

I am trying to figure out a way to automatically update the fix version on issues when they are completed. The issue is that we have 2 products on the same board which have different Releases. I need to update the fix version field to the next unreleased version, but, it needs to be filtered to align with the correct version based on the name. 

For example, I need to filter the fix version that is added to refer to the naming of the version so the one added is Fix Version 1 below. 

Fix Version 1: 2022.10.01

Fix Version 2: Product - 202243

[Hughie Campbell]

When it comes to issue automation, particularly updating the fix version based on version naming conventions, having a streamlined approach can save a lot of time and ensure consistency across your projects. One effective method is to implement automation rules within your issue tracking tool that trigger updates based on specific version name patterns or criteria.

For instance, you can set up a rule that automatically updates the fix version field when a new version is created or when the issue transitions to a specific status. This can be particularly useful if your version names follow a predictable pattern, like Release-2024.1 or Sprint-15.

For a deeper dive into how you can optimize your automation processes, I found an insightful article on https://deltaexecuter.com/ that covers various strategies and best practices. It’s definitely worth checking out if you’re looking to enhance your automation setup.

[Bill Sheboy]

Hi @Keary Norcio 

If I understand your use case correctly, there is nothing built-in to easily do this selection of an arbitrary unreleased version unless you explicitly select the name.

A couple of work-around approaches with automation rules are:

• If your version names have a standard naming convention, and you can build the "next" version based on known information in the issue fields, you could create the smart value expression and just use that.  For example, let's say the Product name is stored in an issue field and the "next" version is based on some date/time information, like year and week, you could build the version name to select it.
• If you only know some of the data to identify the "next" version, let's assume Product, but do not know the rest, you could try calling the REST API to gather all possible versions and search for the one you need.

Kind regards,
Bill

[Keary Norcio]

@Bill Sheboy That you for your recommendation. I will look into both of those options. Both versions are somewhat consistent being either the end of the week or the product name followed by the current week. There are some exceptions when we have hotfix items as that will add a .1 to the end of the product version naming convention, but otherwise are consistent. 

[Seifallah Bellassoued]

Hello @Keary Norcio

Can you explain what do you mean by "based on the name" ?

Otherwise, from the issue how can you now the corresponding fix version ? 

Reagrds,

Seif