Common problems with Jira Software Server on Zapier
- Tables
-
Product updates
Product updates: January 2023 Product updates: March 2023 Product updates: February 2023 Product updates: April 2023 Product updates: May 2023 Product updates: June 2023 Product updates: July 2023 Product updates: August 2023 Product updates: September 2023 Product updates: October 2023 Product updates: November 2023 Product updates: December 2023 Product updates: January 2024 Product updates: February 2024 Product updates: March 2024 Product updates: April 2024 Product updates: May 2024 Product updates: June 2024 Product updates: July 2024 Product updates: August 2024 Product updates: September 2024 Product updates: October 2024 Product updates: November 2024 Product updates: December 2024 Product updates: January 2025 Product updates: February 2025 Product updates: March 2025 Product updates: April 2025 Product updates: May 2025 Product updates: June 2025 Product updates: July 2025 Product updates: August 2025
- Zaps
- Your Zapier account
- Interfaces
- Canvas
- Chatbots
- Getting started
- Agents
- MCP
- Built-in tools
- Lead Router
- Apps
Table of Contents
I'm getting a 401 Error
For some instances of Jira Software Server, 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 Software Server.
I can't configure the Application URL
The "accepted external application URLs" feature of Jira Software Server/Atlassian products is not compatible with Zapier. It’s not possible to configure the application URL.
SSL Error (authorization failed: Could not verify SSL certificate)
If you are running into the above error, it's likely your SSL certificate is from a CA that cannot Zapier recognize or has some issues. For more information, read our SSL certificate guide.
I want to send a link to the Jira Software Server issue to my action app
If you create a Jira issue in a Zap, the action results will not include the new issue URL. However, you can create this URL by combining the base URL and the Key field. The Key field is part of the action results data.
https://{{OrganisationName}}.atlassiant.net/browse/{{Key}}
When creating the URL:
- Replace {{OrganisationName}} with your organization name. You can locate this information from your address bar in your web browser, while logged into Jira.
- Replace {{Key}} with a mapped field containing the Key field from the Jira Software Server Create Issue step.
Error: "The issue type selected is invalid."
This error occurs when selecting the incorrect issue type in the Issue Type dropdown field. This happens if the issue type selected is not associated with your project.
Depending on the setup of your Jira account, there may be multiple types of epics, stories, and tasks available to select from the Issue Type dropdown menu. This is because each project has a custom issue type, created to fit the specific needs of each project, which will appear as "duplicates".
To fix this issue:
- Select a different issue type.
- If you see fields appear within the Zap editor, this means you’ve selected the correct issue type for your project and you can continue to set up your Zap.
- If you see the “Remove these extra fields” this means you’ve selected the issue type not associated with your project.
- Click Remove these extra fields.
- Click Refresh fields
- Select another issue type from the dropdown menu until fields associated with your issue type appear.