I am trying to connect Jira with Zapier but when I get passed the screen where it shows what I’m allowing Zapier to manage within Jira, it gives this error: No Authorization found for site https://neighbornetwork.atlassian.net. Please reconnect your account and select your site when authorizing.
Any ideas on how to fix this? I am the Jira owner/admin of our cloud instance.
Best answer by SamBBest answer by SamB
Hi @johanna5 👋
I just came across your posts here, did some checking and found a bug report for this error which matches what you’re running into here. So I’ve gone ahead and have added you to the list of folks being impacted by this issue.
In the meantime, as Jammer mentioned the only known workaround is to enter the site name exactly as it appears in Jira not as it appears in the URL. For example if you have the site name of NeighborNetwork in Jira and in the url it appears as neighbornetwork.atlassian.net you’d enter it as NeighborNetwork when connecting: I know you’ve already mentioned that the case matches but wanted to share the above example here for anyone else that comes across this and is having similar issues.
I don’t have an ETA on when this issue will be resolved by but we’ll be sure to notify you by email as soon as it is! 🙂
I tried in a different browser and a private browser and no luck. I don’t see anywhere to do what it's asking. That’s the question I have - how to resolve the error message.
Let me see if I can shed some light on this error. Can you try to check the subdomain for Jira?
Because in most cases. It is likely that for most Jira accounts, the site name and subdomain in the URL match precisely so that it will pass the authorization.
Let me see if I can shed some light on this error. Can you try to check the subdomain for Jira?
Because in most cases. It is likely that for most Jira accounts, the site name and subdomain in the URL match precisely so that it will pass the authorization.
Let us know if that fixes your issue. Thanks.
the case matches what it is - I get to this screen and tap accept...so it appears its recognizing the right sub-domain.
And then once I hit accept that is where I get this error:
I just came across your posts here, did some checking and found a bug report for this error which matches what you’re running into here. So I’ve gone ahead and have added you to the list of folks being impacted by this issue.
In the meantime, as Jammer mentioned the only known workaround is to enter the site name exactly as it appears in Jira not as it appears in the URL. For example if you have the site name of NeighborNetwork in Jira and in the url it appears as neighbornetwork.atlassian.net you’d enter it as NeighborNetwork when connecting: I know you’ve already mentioned that the case matches but wanted to share the above example here for anyone else that comes across this and is having similar issues.
I don’t have an ETA on when this issue will be resolved by but we’ll be sure to notify you by email as soon as it is! 🙂