Skip to main content

Hello.
When following the documentation at:
https://help.miro.com/hc/en-us/articles/360019501754
We did all the steps few times and still could not connect jira!
So, the problem is at step 2 "webhook". When we check "Create a webhook automatically (JIRA administrator permission is required)" and click connect:
We receive an error "insufficient permission" and in console there is an error of 403(our jira is publicly accessible so there can not be firewall problems or ...).
When we try to do it manually: there is NO WEBHOOK URL to copy (please see attached screenshot).


Does anyone knows how to fix this since we need to start a project TODAY!

Thank you in advance
Cheers

Hi @Kummer,

It’s great you also reached out to the Support team (here’s an article about this: Do I Need to Contact the Support Team or Ask the Community?).

For those who experience the same issue, here’s the Support team’s reply:

In order to connect Miro to Jira Cards, you need to gain Admin rights on the account (=team): How to Set Up and to Uninstall Jira Cards.

Also, currently, there is a bug on our side that prevents users from creating a manual webhook. We escalated it to the Tech team and will keep you posted on our progress. Please bear with us!

In the interim, we suggest you create an automatic webhook.


I am encountering exactly the same problem reported by Kummer

It doesn’t appear possible to create a webhook automatically or manually

The automatic method fails with a 403 response:
VM6:1 GET https://miro.com/api/v1/accounts/3074457345843444119/integrations/jira/auth/params?baseUrl=https%3A%2F%2Fjadesoftware.atlassian.net%2F&manuallyWebhook=false 403
The manual method is not usable because the WebHook URL field is empty.

re:
>Also, currently, there is a bug on our side that prevents users from creating a manual webhook. We escalated it to the Tech team and will keep you posted on our progress. Please bear with us!

What is the status of this issue please? Is there a public bug tracking reference we can use to look at the status?


Hi @Hugh McColl,

No, I'm afraid, there’s no public bug tracking. Please reach out to the Support Team directly :pray_tone2: