We've spent way too much time trying to figure this out. Scenario:
We've tried so many different variants on trying to get this to work, but nothing has.
Possibly relevant information: we have another automation rule (using the built-in automation, not this plug-in) that automatically applies a label on every ticket, based on the facility entered in the ticket. We thought perhaps that not including labels in the above automation might allow the new linked ticket to pick up a label based on the facility being copied over in step 3 above, but that didn't work either.
We're at our wits end trying to get this to work. Any ideas? If you need more info from me, please just ask.
Thanks,
Kirby
Hi @[deleted]: Did my response provide you with enough information? Is the known bug what's happening here?
Hi Kirby,
What trigger are you using for this rule, is it issue transitioned? It looks like earlier in the rule you're creating an issue, is that correct?
And are any other rules being triggered by this rule?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Here are all the steps:
Everything works as desired except the final step. We also tried adding the label field to step 5 and copy from Trigger issue there, but that didn't work either.
Basically, we're able to copy all information we need from the Trigger issue except for labels.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kirby,
Could you please raise a support ticket for this, it will make it easier for us to assist you. Thanks for the update. An Issue Created trigger is still dealing with a transition so it could be this bug. Can you reproduce the issue and then restart your jira instance? If the label appears on the restart then it is the bug I mentioned. If you can update us on this test in a support ticket that would be great.
Cheers,
Simeon.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Simeon,
Below is a composite screenshot of the step in question. It's one of many variants we've tried to get it to work, but it was our original approach. The top image is what shows in the long list of steps, and the bottom image is the selections I made for the Edit issue fields part. Let me know if you need anything more to make it clearer.
Thanks,
Kirby
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kirby,
We have a known bug in Jira, AUT-1107, which it sounds like you're running into. I cannot be certain without seeing your rule however. If you are able to post a screenshot of the rule or raise a support case and provide it in there I can tell you for certain.
Cheers,
Simeon [Automation for Jira]
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.