Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

JIRA Automation: Error when creating a version Edited

We have a JIRA automation, as an incoming webhook, that does the following:

  1. Create version called {{webhookData.releaseVersion}}
  2. For each issue in the payload assign the version

When we run this, more often than not, we see the following error in the audit log:

Create version

Failed to create version .
A version with this name already exists in this project. (name)
Successfully created version .
Version already exists. Continuing the rule with this version.

Edit issue

Issues edited successfully
JDX-423, JDX-425, JDX-420, JDX-436, JDX-393, JDX-417

 There is only one execution of the rule and we end up with two versions in JIRA... one that has no issues assigned and one that has all of them assigned.

Here's some screenshots:

Automation Rule:

Screenshot 2021-05-17 at 13.59.52.png

Audit Log:

Screenshot 2021-05-17 at 13.58.50.png

Any ideas what might be causing this?

2 answers

1 accepted

0 votes
Answer accepted

"Gather issues from request" is an implicit "branch" (a loop). It executes the rest of the actions once per issue found in the received data.

That means if the webhook data contains 5 issues, automation will attempt creating the version 5 times. It'll only succeed only once (as it appears conflicting version names are not allowed) and it will assign all of the issues to that version.

Other than the error, it sounds like your automation is executing as expected.Iis that accurate?

Yes, that's right. Although we get 2 versions created regardless of how many issues are in the request.

wwalser Atlassian Team May 19, 2021

I presume if there is a single issue in the webhook, the create is only attempted once.

Two and beyond only print the success message once and the error message once? If that's the case then it must be true that we're deduping error/warning messages in the audit log to keep noise down. I've not noticed it in the past but that fact wouldn't shock me.

Hi @Iain Short 

Would you please post an image of your complete rule and one of the audit log for an execution where the symptom occurred?  That may provide context for the community to offer ideas.  Thanks!

Best regards,


Sure. I've updated the issue to include screenshots. Thanks.

Thanks for posting your rule, @Iain Short 

I agree with @wwalser about the built-in branch processing for that webhook trigger.  If the error is misleading/confusing your team, you could instead:

  • use the generic webhook trigger (no issues),
  • create the version,
  • parse out the issue key list out of the data with string and list functions, and
  • use a branch on JQL for the issue key list to update the items' version.

That should result in only one attempted call to create version.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

Introducing External Collaboration for Confluence

We’re excited to introduce external collaboration for Confluence, now available in early access. It is available to preview for Confluence Cloud Premium and Enterprise customers. (If you're not on ...

122 views 0 4
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you