Possible Issues with Atlassian Integrations

1. Your Jira is on a private network / your company firewall blocks external network connections / You are using SSO with your Jira.

2. You use a proxy.

3. There is an issue with your SSL certificate (self-signed certificates are not supported).

1. Add our NAT Gateway IP addresses to your whitelist. Our servers will connect to your network via the static IP addresses.
*Note that if you check our IP addresses using nslookup, the results will return our load balancer's addresses which may vary and change over time. 
* If you also need to allowlist the port numbers we use, they can be found here.

2. Configure a reverse proxy allowing us access. Be sure to fill in the Jira URL field in the account settings with the address that we can access (the address may differ from the actual address of your restricted Jira). You may also want to prolong the timeout value on your proxy server.
The list of endpoints can be found here: Jira Cards FAQ. 

3. Check the SSL certificate that is active on the Jira server. This tool might be helpful: enter your Jira URL and see the results of the connection check. Example: the certificate may be correct (the Certificate in green) but the server certificate chain may be incomplete (Key exchange in yellow) therefore our system gets a response that the certificate needs to be updated.
Refer to this site to resolve issues.

1. You have missed some steps in the link or webhook configuration.

2. You have installed Jira Addon instead of configuring the link for Jira Cards.

1. Try and start from scratch making sure to follow the steps. If you chose to create the webhook manually try creating it automatically.

2. Install the Jira Cards integration following this step-by-step instruction.

Our cards will not work with these versions due to this Jira bug. Please update your Jira to the latest version.

1. You use Jira server versions 7.6 or higher.

2. Your profile is not allowed to edit the Jira issue in question.

1. Edit icon may not be displayed for Jira Server starting from 7.6 due to a security update in this version.

2. Check if you can access the edit mode having opened the issue on the Jira side.

• Please switch to the Incoming Authentication, this is the tab that needs configuring.
• If you cannot switch/skip the step, add temporary values. You can enter any values - you will be able to remove them later: when on the page with your Application links' list click to Edit Miro Cards link and remove the temporary values. Incoming Authentication is the only tab that needs to be configured by the end. 

• Due to the way our integration uses cookies your Jira might not allow you to log in from this page.
• Your Jira is under SSO and your IDP does not allow authentication through iframes.

Log into Jira in another browser tab.
Be sure to check that 3rd-party cookies are allowed in your browser.

If you're working in the Miro desktop app we recommend switching over to the Miro browser version at miro.com.

1. There is no Reporter field in the Jira's Create metadata: the field is unavailable on the Jira Create screen for the selected project.
2. The Jira System Admin who configured and connected the integration doesn't have the necessary permission to set the reporter for issues in the selected project.
3. The reporter field is not editable for audit trail and is set to who created the issue.

1. Go to Project settings > Screens and check if the Reporter field is present in the Create screen. 
2. Check the access levels of the Admin in question and ensure they are permitted to set/change the Reporter field in the selected project. 
3. The field being unavailable is expected behavior. 

• Make sure that the Jira System Admin in question is able to open and edit the affected issues. 
• Reconnect the Jira Cards integration: on the Settings page of your Miro account click to Disconnect Jira Cards and then Connect again. This will renew the access scope of the integration.

Your browser does not allow to save third-party cookies.

To enable the embed, click the link in the message or follow the instruction on how to enable the cookies in your browser. This mostly happens with Mozilla and Safari due to their new security policies.