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

How to create and release version using Jira Automation

Tania Schmittou

We are using Releases as a method to group jira issues worked at a specific time together, it is not used for code release.

I have an automation that creates a version, edits the Fix Version field and releases the version but what is happening is one version is created and it is empty after the automation completes. Audit Log shows that issues were found for the create & edit portion. Once it's released, the issues are gone.

Create version.png Release version.png

Accepted answers

Walter Buggenhout

Hi @Tania Schmittou,

In automation, when you want to edit a set of issues, it is best to start a branch in your rule to define those issues and then add the exact actions into that branch.

Since your screenshot is missing the beginning of your automation rule, it's hard to determine how you are triggering it and how you determine the set of issues to edit.

After the create version part, I would expect a branch to start: For .. - you can use a JQL branch to specify the issues you want to edit:

fixversion IS EMPTY AND Status in (Done, Delivered)

And then add the edit action to fill out the fix version into that section of the rule.

Hope this helps!

All comments

Walter Buggenhout

Hi @Tania Schmittou,

In automation, when you want to edit a set of issues, it is best to start a branch in your rule to define those issues and then add the exact actions into that branch.

Since your screenshot is missing the beginning of your automation rule, it's hard to determine how you are triggering it and how you determine the set of issues to edit.

After the create version part, I would expect a branch to start: For .. - you can use a JQL branch to specify the issues you want to edit:

fixversion IS EMPTY AND Status in (Done, Delivered)

And then add the edit action to fill out the fix version into that section of the rule.

Hope this helps!

Trudy P Claspill

Hello @Tania Schmittou

Can you show us the complete automation rule? There are steps before the Create Version step that we need to see.

I think the problem relates to the context in which the Edit Issue and Release Version steps are running, but I need to see the rest of the rule to confirm.

The Edit Issue action needs to be executed in a context such that each issue is accessed and edited.

The Release Version action needs to be executed in a slightly different context so that the action is executed just once after all the issues have been edited.

With the portion of the rule you are showing, I don't think you have structured the rule correctly to do that.

Tania Schmittou

Hi Trudy! Here is my trigger, I did validate the query and got the expected issues that I anticipated. As stated the Create Version does pick up all the issues and the Edit in my automation does set the Fix Version value.

Tania Schmittou

Hello Walter, please see my reply to Trudy above. thanks!

Trudy P Claspill

Hello @Tania Schmittou

Is that the only step that comes prior to what you showed in the original image?

Are there any steps after what you showed in the original image?

So each week you want to create a new Version/Release, add to that release the issues that are not in any other release and match additional criterial in your Trigger JQL, and then set that new Version to "Released". Is that correct?

Can you show us the details of the Audit Log for the execution of the rule?

If my summary of your intentions for the rule are correct, then your rule is constructed incorrectly.

With a Schedule trigger that includes a JQL, each action in the rule after the trigger will be attempted for each issue returned by the JQL. In that case for each of the 1..n issues returned by the JQL, your rule is trying to execute both the Edit Issue and Release Version actions.

In this case I would recommend removing the JQL from the trigger and instead use a Branch (For Related Issues / JQL ) to retrieve and edit the issues, and move the Release Versions action outside of the branch.

Tania Schmittou

Thank you Trudy. I didn't catch that the release version was inside the if statement and have moved it out. When I executed this previously, a version was created as Unreleased with all the issues in it so it appears the JQL from the trigger worked fine for that portion of the automation so unsure why I would need to do a branch and JQL instead.

The release version is supposed to find (by default) the most recent Unreleased version and release it and this should be the version just created. I will try this now that the release has been moved out of the loop and if that does not resolve my problem, I will move the JQL out of the trigger and do a branch as both you and Walter suggested.

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

automation