Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Jira automation: How to copy existing FixVersions to another label?

Triet Bui Minh
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 2, 2022

In Jira Automation, I cannot find a solution for this use case:

- Each time you change a Fixed Version (might be multiple), for example 1.2.0

- Then I need to add the label "droid_v1.2.0" to the Label field.

- If there is no Fixed Version, then just let the Label empty.

I will appreciate if someone can give me a working Automation Rule.

Edit 1

I end up with such smart values:

{{"(\d+.\d+.\d+)", "droid_v$1").remove(",")}}

It works as expected:

- Set multiple versions: 12.6.0, 13.1.0, 12.6.2

- Then, the Label (Release tags) will be also added: `droid_v12.6.0`, `droid_v12.6.2`, `droid_v13.1.0,` (see the second screenshot)

However I notice there is a comma at the last item in the Label fields (in the below screenshot, it was named Release tags).

Although I add `.remove(",")` but it doesn't work.

Do you know why there is such comma, and what's the correct way to remove it?




2 answers

1 vote
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 2, 2022

Hi @Triet Bui Minh ,

what have you come up with so far? Below is a snippet from the Automation documentation associated with fix version smart values. If you look at the example the use {{name}} to extract the version name. You should be able to fit catenate that into the desired label. However, will you trigger this in fix version being updated? How will you deal with multiple versions? I can see the screen bit complicated possibly. Maybe a better question is why are you seeking to do add the FV as a label? Why can you not simply use the fix version? I'm sure there's a reason I just don't fully appreciate it yet.



Used to access the values in an issue's Fix Versions field. Because this smart value deals with multiple items (i.e: issues can have many fix versions), it can be used with the # symbol to apply the rule to each individual fix version. Learn more about using smart values with sections and lists.

Available properties

  • {{}} - Returns the name of the fix version.

  • {{issue.fixVersions.description}} - Returns the description of the fix version.

  • {{issue.fix.Versions.archived}} - Returns true if the fix version is archived, and false if not.

  • {{issue.fixVersions.released}} - Returns true if the fix version is released, and false if not.

  • {{issue.fixVersions.releaseDate}} - Returns the fix version's release date. Can be combined with other date and time smart values. Learn more about date and time smart values.


In the below example, we list each fix version that the issue has been added to, followed by the version's release date, in bullet point form.

  1. This issue is part of the following releases
  2. {{#issue.fixVersions}}
  3. * Fix version: {{name}}, released on {{releaseDate}}
  4. {{/}}
  5. // returns
  6. This issue is part of the following releases:
  7. Fix version: Version 1.1, released on 2019-08-10T00:00:00.0+0000
  8. Fix version: Version 1.5, released on 2019-08-02T00:00:00.0+0000
Triet Bui Minh
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 3, 2022

Thanks @Jack Brickey for these useful links.

I've updated the original question with more details, as well as the smart values which I use to update the value of Label field. Could you look at it again?

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 4, 2022

Hi @Triet Bui Minh 

First thing, I echo the question from @Jack Brickey : what problem are you trying to solve by having both the label and the fixVersion reflect the same information?

Next, when using search/replace, regular expressions, and lists in automation rules...the audit log is your friend.  Try writing the expression incrementally and writing the pieces to the audit log, step by step.  That will identify what is happening.

Specifically, I suspect that your parsing is leading to an non-empty list value at the end, which could possibly be removed (for the trailing comma) with substringBeforeLast(","):

Kind regards,

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events