I’m trying to automate the creation of several issues when a release is created in the release hub.
This is working as expected.
However, I’m also trying to set the Fix Version in the automatically created issues to the release version i have just created. This isn’t working?
The only option I seem to have in the automation rule is ‘Add Fix Version from Trigger Issue’ but the automation wasn’t triggered from an issue!?
Any ideas?
Hi @Paul Brown - The Fix Version field is not available to you for the set field value when creating the new issue?
I am able to select the Fix Version - it is an available field for me>I Am able to select the Fix Version - it is present for me?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi John, I think the issue is that the Automation was triggered from a create version event and not an issue event, and the action is to 'Add Fix version from Trigger Issue' as this is not a trigger issue, then i'm guessing the fix version isn't known? Was wondering if there was any other way of adding the new version to the tickets it's creating?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Wouldn't the version created in the Version created trigger be the trigger issue?
I would just test that and see what happens with a Test release creation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Paul Brown
Yes, and... to what John said: the newly created issue is the triggering issue. So try that and see if it works.
Occasionally the newly created issue is not fully available at the time the trigger fires, and so copied fields do not always populate. The work-around for that is to add an action to Re-fetch the issue immediately after the trigger; that will reload it before you use it as a copying source.
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Bill Sheboy , @John Funk - I've worked it out - i should have been using the {{version.name}} smart value and not the options in the drop down! All working now, thanks for the support.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Great; I am glad that is working for you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.