If you're running into an error that says "Your JIRA credentials are invalid, or have been temporarily disabled by Atlassian", this is likely due to 2FA being enabled on your JIRA account. You’ll need to disable 2FA on your JIRA account as the current JIRA integration doesn't support their 2FA authentication flow. In the case that you're using Google and 2FA to log into JIRA, please try logging in with your full email address and an API token instead of a password.
If you use Google SSO, then you can connect to Zapier using the same guidelines outlined here, The only difference is that you'll want to use your full email for username, and the API token as the password. Other SSO services haven't been tested yet.
Currently Zapier supports JIRA 6+. We support both JIRA Cloud and Server.
If you're seeing errors like this "Max retries exceeded with url: /rest/auth/1/session (Caused by : [Errno -2] Name or service not known)" then it is possible you have not opened up access to JIRA to the open internet for Zapier to connect.
A common setup is for JIRA to be configured to only allow internal company traffic, which would mean Zapier would be unable to connect.
You'll need to make sure that Zapier's IP addresses are whitelisted. We use Amazon's AWS products for our server infrastructure, so you'll need to whitelist the IP list from the us-east-1 region.
AWS provides a list of their IP address ranges at https://ip-ranges.amazonaws.com/ip-ranges.json.
For some instances of JIRA, you need to log in with your user name instead of your email. You can find your user name by going to your profile in JIRA.
The "accepted external application URLs" feature of JIRA/Atlassian products is not compatible with Zapier. Basically - if you are trying to connect via this page:
You are trying the wrong thing!
If you are running into the above error, it's likely your SSL certificate is not from a CA Zapier recognizes or has some issues. For more information please see our SSL guide here.
JIRA doesn't provide the URL as one of the fields, but you can build the URL yourself by combining the base URL and the Key field like so:
This is a known bug in JIRA that you can track here.
You'll need to reconnect your account and use 'https:' in the base url here:
To remedy this:
- Choose any issue key from the Issue Key dropdown menu.
- Map values into the fields as desired.
- Go back up to Issue Key dropdown and set it to use the issue key mapped in in the previous step.
- Turn on your Zap or test your action—the dynamically updated issue will get the values you've mapped.
You will need to go to the configurable screen for the project you have selected, to add this field. The URL will be something like this:
JIRA might present you with multiple identical-looking Issue Types with different ID numbers, like this:
Clicking on the wrong Issue Type here will prevent the rest of your fields from loading, and you will not be able to create an issue. When you see this, click through the variations of the Issue Type that you want, until you see the rest of your fields load into the template in your Zap. This will help show you that you've selected the correct instance of the Issue Type for your project.