Jira Software Server Help & Support
What JIRA Triggers and Actions Are Supported
What Triggers and Actions are Supported?
- New Priority - Triggers when you add a new priority.
- Updated Issue - Triggers when an issue is updated.
- New Issue (Via JQL) - Triggers when a new issue is added that matches some JQL.
- New Project - Triggers when a project is added.
- New Issue Type - Triggers when you add a new issue type.
- New Issue - Triggers when you add an issue to a project of your selection.
- Find User - Find a user by name.
- Find Issue - Searches for an issue, either using the issue's key, or its summary.
- Attach File to Issue - Attaches a file to an existing (or newly created) Jira issue.
- Add Watcher to Issue - Adds a user to the issue's watcher list.
- Update Issue - Updates an existing issue.
- Create Issue - Create a new issue, select your own project and issue type.
How to Get Started with JIRA on Zapier
When you start creating a Jira Software Server Zap, you will be asked to connect your Jira Software Server account.
When you click connect, you will then be asked to enter your Jira Software Server username and password.
Note: In order to connect your JIRA account to Zapier, you will need full admin privileges along with API access. You can find out more about granting the correct permissions here.
If those steps were correct, you'll get sent back to your Zap where you will now have your Jira Software Server account successfully connected!
Popular Things To Do With JIRA
Common Problems with JIRA
I can't connect to my JIRA account#
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.
I use Google or some other SSO to login to JIRA, how can I connect my account to Zapier?#
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.
What versions of JIRA are supported on Zapier?#
Currently Zapier supports JIRA 6+. We support both JIRA Cloud and Server.
Help! I Cannot Connect With My Instance#
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.
I'm getting a 401 Error#
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.
I can't configure the Application URL#
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!
SSL Error (authorization failed: Could not verify SSL certificate)#
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.
I want to send a link to the JIRA issue to my action app#
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:
Some of my issue type's custom fields are missing#
This is a known bug in JIRA that you can track here.
My zaps are erroring out with a 301 error#
You'll need to reconnect your account and use 'https:' in the base url here:
The "Update Issue" action doesn't provide my custom fields if I'm using a custom issue key#
To remedy this:
Choose any issue key from the Issue Key dropdown menu.
- If the dropdown doesn't load any issues:
- Select "Use a Custom Value (advanced)" from the Issue Key dropdown
- In the Custom Value for Issue Key ID input box, type the key for a valid issue in your Jira account
- Click the Refresh Fields button at the bottom of the screen. Your custom fields should now appear
- If the dropdown doesn't load any issues:
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.
- You will see a warning about extra fields in the action—disregard this
Turn on your Zap or test your action—the dynamically updated issue will get the values you've mapped.
Error: "Field '(some-field-name)' cannot be set. It is not on the appropriate screen, or unknown."#
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:
Error: "The issue type selected is invalid."#
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.
Need More Help? - Our support team is happy to help -- send us a message