Thanks @andywingrave for your reply. Yes, support got back to me on this. It turned out to be a bug in the Zapier integration with Jira Cloud Software. It happens when you try to use more than one Jira site in different Zaps.
When adding a Jira instance as a connection, it always adds the top most Jira instance from the drop down field regardless which is actually selected. The topic below was the same, and the bug was reported a year ago, but it seems like it is still not fixed…
I’m sorry to say that this bug hasn’t yet been fixed. I’ve added you to the issue report, which lets the team know how many users are affected by it and also that we will send you an email when we have an update.
I wanted to swing by with a belated update and share this bug was recently closed.
Here’s a bit that was shared in the outbound email:
I’ve got great news for you: we have added the ability to specify which cloud site you want to connect to. Now your Zaps can run on the cloud site of your choosing, instead of having our system choose for you.
There’s nothing you need to change in your existing Zaps. But if there were some Zaps you were holding off on making because you wanted to use a different cloud site, go ahead and set those up. You will need to connect a new JIRA Software Cloud account in order to specify your cloud site.
Here's some example screenshots of my account connection process: 1.
2.
Thanks as always for flagging this in community and happy zapping! ⚡️
+9
+12
