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; } } }

Automation to release specific fix version fails to find a match

Joshua Tilton

We have automation in place when we create a specific issue type for a HotFix that creates a Fix Version with a specific name. This automation is performing as it should and assigns the name, the start date and, if we want, a release date (tested with and without in case it was affecting the ability to release the version through automation).

Unfortunately I am unable to determine the proper setup to release that fix version when the ticket is moved to "Done". The automation fires, but it fails to find a matching version. Here are the steps I am using, the comment portion was a "debug" and returns the expected fix version name, so I am unsure why the final step fails:

The Audit Log shows:

When I look at the comment it has, for all three smart tags, the expected version name.

Accepted answers

Bill Sheboy

Hi @Joshua Tilton

To reference a version as a smart value for the Release Version action try using the id instead of the name:

Also, do you ever expect there to be multiple fixVersion values assigned for this issue? How about no values? If either case applies please update your rule accordingly.

Kind regards,
Bill

All comments

Stefan Salzl

Hi @Joshua Tilton

could you please show the whole automation rule? Are you sure the fixVersion is set in the issue ? I can reproduce this when there is no unreleased fix version.

Best
Stefan

Bill Sheboy

Hi @Joshua Tilton

To reference a version as a smart value for the Release Version action try using the id instead of the name:

Also, do you ever expect there to be multiple fixVersion values assigned for this issue? How about no values? If either case applies please update your rule accordingly.

Kind regards,
Bill

Joshua Tilton

The automation asks for the name, this is my my recent attempt using just {{triggerIssue.fixVersions}}:

I tried the ID with the same result. The issues all have a single fix version applied, that version is successfully create by Automation when the ticket type is created. Unfortunately I don't know a way to test the automation outside of the workflow to verify, so I have to wait until we have a live scenario.

Joshua Tilton

Here is my rule, with some redactions for security:

And here is the Audit result:

The "Comment on Issue" portion returned the expected Fix Version Name using any of the 3 smart tags, but none of those worked in the final step (I've tried 5 different smart tags at least)

Stefan Salzl

Hi @Joshua Tilton

Regarding your 3rd condition: Could those issues that should trigger the release be in different projects?

furthermore:
within your release version action there need to be declared a project where the version should be released. how is the action configured? Did you check/can you make sure that the version is unreleased at the time of release attempt/automation rule activation?

and:
regarding your predecessor automation rule: is the hotfix version created in the same project?

Best
Stefan

Bill Sheboy

First thing: I would create a test project to experiment with a rule like this. That can allow faster development and safer testing. When done, you may copy/edit the rule into the target project.

This rule worked for me using the version's name when I explicitly selected the Project from the drop-down in the Release Version action.

trigger: issue transitioned to done
advanced compare condition...to check if there is one-and-only-one version to release
- first value: {{issue.fixVersions.size|0}}
- condition: equals
- second value: 1
action: release version
- specific version name to release: {{issue.fixVersions.name}}
- project: I selected the project matching the trigger issue/rule location

Joshua Tilton

The release is still unreleased when the issue is transitioned to "Done"

The issues that trigger the release are always in the same project as the release, it is a 1:1 relationship.

Issue is created, release is created via automation
Issue proceeds through workflow
Transition to "done" fires release automation which fails to find a matching release that was created in step 1, although the name of that release can be logged as a comment successfully.

It appears the automation of releasing by release name has a fatal flaw where Name is perhaps not how they should be referencing it, but that field is not editable.

Joshua Tilton

Changing the value to {{issue.fixVersions.name}} and not specifying a particular one (first, last etc) did the trick!

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-software

jira-software-cloud

automation

smart-value