nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issue with Automation Rule for Creating Release Version in Jira

Sundram Trivedi

Problem Statement: I have created an automation rule that triggers when a sprint is closed. It automatically releases and creates a new version. I also plan to extend this rule to add release notes on Confluence. However, I am facing an issue with generating the correct version name.

Current Setup: My sprint closes every second Friday. When the sprint is closed, the rule should create a new release version. The version name format should follow this pattern: Current version: TWX202503.1 Next version: TWX202505.1 Following versions: TWX202507.1, TWX202509.1, … TWX202601.1, etc.

Issue: The version name is not being generated as expected. I suspect there may be an issue with the automation rule logic.

Request for Help: Cross-check my rule – If there are any changes needed, please suggest modifications. Correct version name logic – How can I ensure that the version name follows the expected pattern? Any guidance or example automation rule adjustments would be highly appreciated. Thanks in advance!

Accepted answers

Bill Sheboy

Hi @Sundram Trivedi

What do you observe happening that is not working as expected? Please post an image of the audit log details for the rule execution (will all of the area at the right side of the log expanded).

Until we see that...

For scenarios like this, I recommend posting the complete expression used to form the new version name. That will make it easier for the community to offer suggestions.

And, I recommend breaking up the creation of the version name into steps, perhaps storing the values with Create Variable, and writing them to the audit log. That will help you progressively confirm / adjust the logic to create the new version name.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Sundram Trivedi

What do you observe happening that is not working as expected? Please post an image of the audit log details for the rule execution (will all of the area at the right side of the log expanded).

Until we see that...

For scenarios like this, I recommend posting the complete expression used to form the new version name. That will make it easier for the community to offer suggestions.

Kind regards,
Bill

Sayed Bares [ServiceRocket]

@Sundram Trivedi can you share with us the full expression for version name? what is the output when you run the automation?

Sundram Trivedi

Hi @Sayed Bares [ServiceRocket]

This is the audit log:
In the audit log, it shows "Version already exists," which is the same version that was recently released.

Variable name: TWX{{now.format("yyyyMM")}}.{{#=}}{{latestVersion.name.split(".").1}} + 1{{/}}

Sundram Trivedi

Hi @Bill Sheboy ,

In the audit log, it shows "Version already exists," which is the same version that was recently released.

Variable name: TWX{{now.format("yyyyMM")}}.{{#=}}{{latestVersion.name.split(".").1}} + 1{{/}}

I tried implementing the Create Variable approach by first storing the version name in a variable and then using it to create the version. However, I am still facing the same issue—the version is not being created as expected, and I am getting a different version name.

in this variable name is : TWX{{now.format("YYYY")}}{{#=}}{{lookupVersions.name.sort.reverse.first.substring(7,9)}} + 2{{/}}.1

Smart value: TWX{{now.format("YYYY")}}{{#=}}{{lookupVersions.name.sort.reverse.first.substring(7,9)}} + 2{{/}}.1

Bill Sheboy

There is no smart value named {{latestVersion}}. What are you expecting that value to contain?

What value is set to the Fix Versions field in the Edit Issue action?

And most importantly...your rule trigger is Sprint Completed. Why not use {{sprint.id}} with the branch JQL to find the issues in the sprint? The Lookup Issues action does not appear to be needed...and could return the incorrect issues than you expect: it will return ALL of the issues in completed sprints (or at least the first 100 of them).

Bill Sheboy

The list functions you show do not exist: sort and reverse. When one wants to order the results of the Lookup Issues action, an ORDER BY clause is added to the JQL.

But that will not help for this scenario because it cannot sort a list-of-lists (i.e., Fix Versions is a list within the lookup issues result, which is also a list)

There is no smart value named {{lookupVersions}}

Let's reset a bit: please describe which version you are trying to create. That is:

Are the issues in the sprint which just completed in one-and-only-one Fix Version? Is that always the case?
You describe two different ways to increment the version number: +1 or +2. What is a list of example versions for your pattern?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud