Resources · Zapier integration

Jira Software Server Zapier integrationAutomate Jira Software Server with Zapier.

The Jira Software Server Zapier integration links your self-hosted Jira to the rest of your tools. It offers 6 triggers, 7 actions and 3 searches, works on the free plan, and every trigger here is checked on a timer rather than pushed.

See the 16 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Jira Software Server Zapier integration actually does

It is a bridge between your self-hosted Jira and Zapier. When something happens in Jira (a new issue, an edited issue, a new project), Zapier notices it on its next check and runs the steps you chose. It also works the other way: other apps can create, update or comment on Jira issues without anyone opening Jira.

Three results teams usually want from it. First, tickets that write themselves: a form entry, an email or a row elsewhere becomes a real issue through Create Issue, with the project and issue type you picked. Second, issues that keep their context: Add Comment to Issue and Attach File to Issue drop a customer reply or a document onto the issue it belongs to, so nobody pastes things by hand. Third, the right people in the loop: New Issue (Via JQL) watches a precise slice of your backlog, and Add Watcher to Issue puts the owner on each matching issue.

Now the honest part. Every trigger on this app is a polling one, so nothing here is instant: on the free plan, a new issue can wait up to 15 minutes before the Zap reacts. There is no trigger for a new comment or a status change on its own, only Updated Issue, which fires on any edit. And there is no delete action at all. If you need something the list does not offer, the API Request (Beta) action is the escape hatch, but it means reading the Jira API.

If you are still choosing a platform, our n8n vs Zapier comparison sets the criteria side by side, and the Zapier review covers the tool as a whole.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every line of this page. Here they are in plain English, once.

Zap
The automation you build: one trigger, then one or more actions that run every single time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for that event to show up.
Action
What the Zap does once it has started: the step that creates, writes, sends or moves something for you in an app.
Task
The unit Zapier bills. One task is one action that your Zap completed successfully; your plan counts those, nothing else.
Polling vs instant trigger
Polling: Zapier asks the app for new items on a timer. Instant: the app calls Zapier the moment it happens. Jira Software Server only polls.
Filter
A step that lets the Zap carry on only when the incoming item meets your condition, and quietly stops it in every other case.
Search step
A step that looks up something that already exists in an app, such as an issue or a user, so later steps can reuse it.
Cost

What it really costs to run

Jira Software Server is not a premium app, so it works from the free plan. What you pay for is tasks, not checks.

  • Premium appNo, available on the free plan
  • Free plan100 tasks per month, two-step Zaps only
  • Trigger checksFree, never billed
  • Failed actionNot counted

The trigger never costs a task, however often Zapier looks for new issues. Each action that succeeds counts as one task, so a Zap with three actions burns three times as much as a Zap with one. An action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger, one action. Add a filter, a search step or a second action and you have a multi-step Zap, which needs a paid plan.

Connect

Connect your Jira Software Server account

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. A connection is your Jira account linked to Zapier once, then reused by every step that touches Jira.

  2. 02

    Pick Jira Software Server

    Type the app name in the dialog, select Jira Software Server (the self-hosted edition, not the cloud one), then click Add connection. A new browser tab opens for the sign-in.

  3. 03

    Sign in and grant access

    Log in to your Jira instance in that tab and allow Zapier to use the account. You need an account on the instance, plus read or write rights on any project you do not own and want the Zap to touch.

First Zap

Your first Zap: new bug, owner watching

GoalEvery new issue in a project gets a named teammate added as a watcher, but only when it is a bug.

  1. 01

    Create the Zap and pick the trigger

    Click to build a new Zap, choose Jira Software Server as the app and New Issue as the event, then select your Jira connection.

  2. 02

    Choose the project

    Project is required on this trigger. Pick the one to watch, then test: Zapier brings back the three latest issues so you map fields on a real one.

  3. 03

    Add the filter

    Click the plus icon, choose Filter, and set the field (issue type), the rule (text exactly matches) and the value. Text rules only work on text.

  4. 04

    Find the teammate

    Add Find User and type the person's name in Keyword. It searches name, email and username, and hands the username to the next step.

  5. 05

    Add the watcher and test

    Add Add Watcher to Issue, map the issue key from the trigger and the user from the search, then run the step once and check the issue in Jira.

  6. 06

    Publish

    Click Publish to switch the Zap on. Remember: a filter plus a search makes this a multi-step Zap, so it needs a paid plan.

Triggers

Jira Software Server triggers

6 events start a Zap when something happens in Jira Software Server. Zapier checks for them at the interval your plan allows.

1

New Issue

Polling trigger

In Zapier“Triggers when you add an issue to a project of your selection.”

Starts your Zap each time someone files an issue in the project you chose. It is the plain, catch-all way to react to fresh work landing in Jira, whatever its type or priority.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
posting every new ticket of a support project into the team chat, or copying it into a client tracker.
Watch out
the trigger covers one project at a time, so watching three projects means three Zaps or the JQL version below.
2

New Issue (Via JQL)

Polling trigger

In Zapier“Triggers when a new issue is added that matches some JQL.”

This one lets you describe the issues you care about in JQL, Jira's own query language, and only those start the Zap. Several projects, one assignee, one label: the query decides, so you rarely need a filter step afterwards.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
alerting a lead only when a blocker lands in any of the projects they own.
Watch out
end the query with order by created desc, as the Jql field help asks; do not skip it.
3

New Issue Type

Polling trigger

In Zapier“Triggers when you add a new issue type.”

Fires when an administrator adds a new issue type to your instance. It watches the configuration of Jira, not the work inside it, so it runs rarely.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
keeping an admin log or a shared sheet of your Jira setup up to date without asking anyone to report changes.
Watch out
it reacts only to types created after the Zap is published, never to existing ones.
4

New Priority

Polling trigger

In Zapier“Triggers when you add a new priority.”

Reacts when a new priority level appears in your Jira instance. Like New Issue Type, it tracks how Jira is configured, which matters when other tools mirror your priority list and must stay aligned with it.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
warning the person who maintains a helpdesk mapping that a new priority now needs a matching value there.
Watch out
it reacts only to priorities added after the Zap is published, never to the existing list.
5

New Project

Polling trigger

In Zapier“Triggers when a project is added.”

Sends a signal each time a project is created on the instance. Teams use it to set up everything that usually follows a new project by hand: a channel, a folder, a line in a portfolio sheet.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
creating a matching client folder and a kickoff task the moment a delivery project appears in Jira.
Watch out
it reacts only to projects created after the Zap is published, never to existing ones.
6

Updated Issue

Polling trigger

In Zapier“Triggers when an issue is updated.”

Goes off when an issue in the chosen project has been edited, whatever the edit was. When only one kind of change matters to you, a filter after it lets the rest go by.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
syncing the status of a ticket back to the CRM record of the customer who reported it.
Watch out
a Zap that updates or comments on the same project re-triggers itself and loops, burning tasks fast.
Actions

Jira Software Server actions

Jira Software Server gives you 7 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Comment to Issue

Action

In Zapier“Adds a new comment to an issue.”

Posts a comment on an issue, so outside information lands right where the team works. Jira's Wiki Markup formatting is accepted in the text.

When to use it
pasting a customer's email reply under the ticket it refers to.
Watch out
map the issue key, not the numeric id; Find Issue can supply it when the trigger does not.
3

Add Watcher to Issue

Action

In Zapier“Adds a user to the issue's watcher list.”

Puts a user on an issue's watcher list, so Jira notifies them of every change. The user is given by username (like jon.snow).

When to use it
making sure the account manager follows every ticket their client opens.
Watch out
the connected account must administer the project, otherwise each run fails.
4

Attach File to Issue

Action

In Zapier“Attaches a file to an existing (or newly created) Jira issue.”

Drops a file onto an existing issue, or onto one created a step earlier in the same Zap. Both the numeric ID and the key work here.

When to use it
keeping the screenshot a tester uploaded to a form next to the bug it illustrates.
Watch out
both the issue and the File field are required, so an earlier step has to hand over the file to attach.
5

Create Issue

Action

In Zapier“Create a new issue, select your own project and issue type.”

Opens a brand new issue in the project and issue type you select, filled with data from earlier steps. It is the action most Zaps for Jira end with.

When to use it
turning each bug report sent through a web form into a ticket in the right project.
Watch out
Project is required, so pick it first; the issue type comes right after.
6

Update Issue

Action

In Zapier“Updates an existing issue.”

Changes an issue that already exists, identified by its key (like XYZ-123).

When to use it
moving a ticket forward once a customer confirms the fix in another tool.
Watch out
if your custom fields do not show up, the field help in Zapier points to a workaround; and never point it at the project your Updated Issue trigger watches.
7

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

An advanced action that sends a raw request to your Jira instance with the connection already signed in. It covers what the other six actions leave out.

When to use it
a developer on the team needs a Jira operation no ready-made action offers.
Watch out
requests only reach domains tied to this app, and Stop on error decides whether a failure halts the Zap.
Searches

Jira Software Server searches

3 search steps look for data that already exists in Jira Software Server, so a later step can use it.

A search step fetches something that already lives in Jira so the next steps can use it. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Some action fields also offer + Add search step, which inserts one and wires it in for you. Remember that a search makes the Zap multi-step.

1

Find Issue

Search

In Zapier“Searches for an issue, either using the issue's key, or its summary.”

Looks up one issue from its key or from its summary, and hands the result to the following steps. Handy when the trigger knows a title but not the key Jira expects.

When to use it
finding the ticket a customer email mentions before commenting on it.
Watch out
when several issues match, the multiple-results setting decides which one goes on, so set it on purpose.
2

Find Issue (Via JQL)

Search

In Zapier“Searches for issues matching a JQL query.”

Runs a JQL query, for example project = "ABC" AND status = "In Progress", and returns what matches. The most precise way to pick an issue from inside a Zap.

When to use it
fetching the open epic of a client project before linking a new issue to it.
Watch out
the JQL field is required, and a query that is too broad returns several issues.
3

Find User

Search

In Zapier“Find a user by name.”

Finds a Jira user from a keyword, checked against name, email and username. It turns an email address from another tool into the username Jira actions ask for.

When to use it
adding as watcher the salesperson whose email arrived with the deal.
Watch out
a common first name can match several people, so search by email when you have it.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and skips the steps that depended on it. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into find-or-create. Jira Software Server offers no such variant, so you will not see it on these three searches.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or pass all of them on at once.
When it breaks

When a Jira Software Server Zap breaks

Most failures on this app come from three places: issue identifiers, permissions, and Zaps that feed themselves.

Zapier keeps a help article called Common problems with Jira Software Server on Zapier; read it first when a step turns red. The cases below are the ones the field descriptions and Zapier's general rules already warn about. For a deeper dig, see Zapier troubleshooting.

  • Key versus numeric id

    Add Comment to Issue, Link Issues and Update Issue expect the issue key (like ABC-123). Map the numeric id instead and the step cannot find the issue.

  • Watcher refused

    Add Watcher to Issue needs the connected account to administer the project. A regular user gets an error on every run, and that run costs nothing.

  • The Zap that feeds itself

    Updated Issue plus Update Issue or Add Comment to Issue on the same project: each write is a new edit, the Zap restarts, and the task count melts.

  • JQL without a sort

    New Issue (Via JQL) wants order by created desc at the end of the query. Add it after your own conditions.

  • No catch-up on old issues

    A Zap only reacts to what happens after you publish it. Issues created before that are never picked up; moving the backlog is a separate job.

  • Bulk imports held back

    A migration or bulk import can return a huge batch at once, and Zapier's flood protection may hold it. The same issue, though, never starts the Zap twice.
Need help

Need help automating Jira Software Server with Zapier?

A person reads every message.

FAQ

Jira Software Server and Zapier: frequent questions

01Is the Jira Software Server Zapier integration free?
Yes, it works on the free plan, because Jira Software Server is not a premium app on Zapier. The free plan gives 100 tasks per month and unlimited Zaps. The catch is the shape of the Zap: on the free plan, each one is limited to two steps, one trigger and one action. As soon as you add a filter, a search such as Find User, or a second action, the Zap becomes multi-step and you need a paid plan. Most useful Jira scenarios, like adding the right watcher, reach that point quickly.
02How many tasks does a Jira Zap use?
One task per action that succeeds, and nothing for the trigger. Zapier can check Jira for new or updated issues as often as your plan allows without spending a single task. A Zap that creates an issue and then attaches a file uses two tasks per run. An action that fails, for example Add Watcher to Issue refused for lack of admin rights, is not counted. The real danger is a loop: a Zap that updates issues in the project its Updated Issue trigger watches restarts itself on every write and eats the monthly count very fast.
03Does Jira Software Server work in real time with Zapier?
No. All 6 triggers of this app are polling triggers: Zapier asks your Jira instance for new items at a fixed interval. That interval depends on your plan: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. On paid plans you can also run a check by hand from the editor. The type is set by the app itself, so no setting in the editor turns these triggers instant, and the app page shows the free-plan interval on each trigger if you want to check it in one click.
04What is required to connect Jira Software Server to Zapier?
An account on your self-hosted Jira instance, plus read or write access on any project you do not own and want the Zap to touch. The connection itself takes three moves: open the Apps page in Zapier, click + Add connection and pick Jira Software Server, then sign in to Jira in the tab that opens and grant access. Some actions ask for more: Add Watcher to Issue only works when the connected account is an administrator of the project concerned.
05Why does a New Issue (Via JQL) trigger miss issues?
Usually because the query does not end with order by created desc. The field help on this trigger asks for that sort explicitly. Add it after your own conditions, keep the filtering as narrow or as broad as you like, and test again. Also check that the connected account can see every project named in the query: an issue in a project it cannot read will never reach the Zap, whatever the JQL says.
06What if the Jira operation you need is not in the list?
The API Request (Beta) action covers that case. It sends a raw request to your Jira instance using the connection you already set up, so there is no extra login to manage. It is an advanced action: someone has to know which Jira API call to make, and requests can only go to domains tied to this app. Its Stop on error setting decides whether a failed call halts the Zap or lets it continue. For a missing trigger, such as a new comment, there is no equivalent shortcut.
07Zapier, Make or n8n for Jira Software Server?
It depends on your criteria, not on a winner. Zapier offers 16 ready-made operations for this app and bills per successful action. If your Jira is self-hosted for data control reasons, a tool you can also host yourself may weigh more than setup speed. If your scenarios need many steps and branches, compare how each platform counts usage before you commit. The interval of polling triggers on your plan is another criterion worth putting on the table.
Same platform

Other docs you might need on this stack.

Browse all integrations