Jira Automation: Cannot create a version with incremental name

[Antonio Carvetta]

Hello team,

I'm trying to create the following Jira automation rule.

When a sprint is created, create a new release version. The naming has to be incremental (i.e. R 1, R 2, etc)

Then set the fix version for each issue with the current release version, and override if it's not empty.

I'm struggling to use the smart values to fill out the release name etc. and seems that the 'Fix version is not empty' condition doesn't work well.

Do you have any suggestions?

[Bill Sheboy · Accepted solution]

Hi @Antonio Carvetta -- Welcome to the Atlassian Community!

Would you please post images of your complete rule and the audit log details showing the execution?  Those will provide context for the community to offer ideas to help.  Thanks!

Until we see those...

What you describe is a fairly common use case, although you do not describe the naming convention of your sprints...and if that can be used to build the version names.

• Often people implement this scenario by creating the new version when the current one releases with one rule.  This makes incrementing easy by extracting the value from the released version.
• Then with a different rule, the next-unreleased-version can be assigned to the issues when the sprint starts
• For your condition to only update the fix version if it is empty, that should be possible with a condition.  Showing the full details of your rule will help identify why that is not working for you.

Kind regards,
Bill

[Antonio Carvetta]

Hello @Bill Sheboy , thanks for getting back to me!
 

I feel I'm using the formula in the wrong way.

Then I set the 'next unreleased version' for all the issues with/out empty version

[Bill Sheboy]

The {{version}} smart value is only available with the version-related triggers, and so your rule cannot use it when triggered on Sprint Started.  Please note the difference as that smart value is singular, as compared to the issue-related smart values of {{issue.fixVersions}} and {{issue.versions}} (which is really the Affects Version field).

To do exactly what you suggest when triggered on Sprint Started, you would need to call the REST API from the rule to get all of the project's versions, get the maximum value from the version names from the webresponse, and then use that to create the next version name.

Because of this additional complexity, I suggested the alternative of creating the new version when the prior one releases, and then just assign the version when the sprint starts.

If you still want to create the version only after the sprint starts, please review this article as which describes how to call the REST API from a rule: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828 and this is the reference for the REST API method to gather all the versions for a project: https://docs.atlassian.com/software/jira/docs/api/REST/1000.824.0/#api/2/project-getProjectVersions

[Antonio Carvetta]

@Bill Sheboy, thanks for clarifying this. I will spend some time on the REST APIs rule.

Do you have an example of the suggested workaround?

The alternative of creating the new version when the prior one releases, and then just assign the version when the sprint starts.

Thanks.

[Bill Sheboy]

The alternative is what I described earlier...So one rule would be:

• trigger: version released
• action: use that version's name to create a new one with the higher number

And the second rule could be:

• trigger: sprint started
• branch: on issues in the sprint
  • condition: fixVersion is empty
  • action: edit issue to assign fixVersion to the next, unreleased version

This approach assumes several things:

1. Your team releases a version before you start the next sprint
2. Your team only has versions matching your naming convention in the project.  For example, R 1, R 2, R 3, etc.
3. The "next, unreleased version" is the one you want assigned to issues in a sprint when it starts
4. You are not using parallel sprints with your Jira Scrum board in this project

[Antonio Carvetta]

Thanks @Bill Sheboy 

I used this automation rule, and it seems to work fine.

What's the best automation rule to override a fix version of an unreleased issue?

Thanks!

[Bill Sheboy]

I believe if you just use the SET option with Issue Field edit the value is replaced for fixVersion.

[Arnab Mondal]

[Plz tell me how can i do this work also and grow with our community also and achive our gols