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:
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
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:
And here we can see its created duplicate releases, its assigned one issue to each release.
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!
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:
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
My goodness, this worked! Thank you for the suggestion Bill!
Best regards,
Spencer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Awesome; I am glad to learn that helped. Have a great day!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.