Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Create Version and Edit Work Item Fields automation creating duplicate Releases

Spencer Shupe
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!
September 18, 2025

Hello!

I've created a simple webhook automation to create a Release in Jira and then assign it to a collection of issues. However I always end up with duplicates of the Release, one Release for each issue key I supply. I've tried re-working the Edit work item fields definition multiple ways but always end up with this problem.

 

This is the workflow definition, the webhook is configured to accept issues in the POST body:

Screenshot 2025-09-18 at 3.18.15 PM.png


And these are the different ways I've tried defining the Edit work item component. All of these still result in creating a Release for each item supplied to the webhook

Screenshot 2025-09-18 at 3.19.21 PM.pngScreenshot 2025-09-18 at 3.20.05 PM.png


This is an example of an audit log for a successful run with multiple issues. In this case the version already existed from a previous test and we can see that the Create Version step has appropriately skipped the release creation:

Screenshot 2025-09-18 at 3.23.37 PM.png


And here we can see its created duplicate releases, its assigned one issue to each  release.Screenshot 2025-09-18 at 3.24.43 PM.png

 

I must be using this wrong but I can't seem to find or figure out what the proper configuration for this would be. The intent is to create one Release with the given name and assign all the issues in the webhook POST body to that Release via the fix version field. Any guidance would be much appreciated!

 

1 answer

1 accepted

0 votes
Answer accepted
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.
September 19, 2025

Hi @Spencer Shupe -- Welcome to the Atlassian Community!

The likely cause the trigger receives work items, and thus it processes the rule steps for each one.  And, because that happens quickly, it creates a racetrack timing scenario where:

  • sometimes the first version create completes fast enough that later attempts find the existing version and do not recreate it,
  • while other times the version create is still in process, and thus multiple versions are created.

One workaround for this scenario is to pass only the work item keys, and not the work items, to the trigger data (changing the trigger's options and request data).  Then in the rule, create the version one time and use a JQL branch to iterate over the work items (with the request data) to assign the versions.

 

Kind regards,
Bill

Spencer Shupe
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!
September 19, 2025

My goodness, this worked! Thank you for the suggestion Bill!

 

Best regards,

Spencer

Like Bill Sheboy likes this
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.
September 19, 2025

Awesome; I am glad to learn that helped.  Have a great day!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events