Only trigger when issues are first moved to this status eg. `Done`.

The `ORDER BY` keyword is not allowed in your query. [Learn more about JQL](https://confluence.atlassian.com/jirasoftwarecloud/advanced-searching-764478330.html).

Only trigger when issues with a particular status are updated eg. `In progress`.

This Trigger does not use one of your [App Connections](https://help.zapier.com/hc/en-us/articles/8496290788109-Manage-your-app-connections) between Jira and Zapier. Instead, Zapier uses the fields below to connect to your Jira account and adds a [Jira webhook](https://support.atlassian.com/jira-cloud-administration/docs/manage-webhooks/) that triggers this Zap.

Your Jira account must have the "Administer Jira" [global permission](https://support.atlassian.com/jira-cloud-administration/docs/manage-global-permissions/).

You can create an API token [here](https://id.atlassian.com/manage-profile/security/api-tokens).

Use this field to trigger on comments in specific projects. If you leave this field empty, the Zap will trigger on comments in all projects.

Use this field to trigger on updated comments in specific projects. If you leave this field empty, the Zap will trigger on updated comments in all projects.

The search by name is not case sensitive and ignores any blank space.

If provided, find the issue with the "best match" of the summary text.

If you already know the issue's key, enter it here and we will look up that specific issue (Example: `XYZ-123`).

Searches the name, email, and username fields within Jira Cloud.

Make sure you map the issue key instead of the ID (e.g. TEST-123 not 12345).

Make sure you map the issue key instead of the id (e.g. TEST-123 not 12345).

Select or search for a user to watch the issue. If no user is specified, you will be assigned as the issue watcher

Make sure you map the issue key instead of the id (e.g. TEST-123 not 12345). Note that if you are using a search for this, you'll need to select a similar field from the dropdown first and then map the issue over as a custom value so that the fields load first.

We can only list available statuses for the issue given in the above field. You may have [workflows](https://confluence.atlassian.com/adminjiracloud/working-with-workflows-776636540.html) in place which can prevent certain statuses from appearing here. Make sure whichever issue is specified above is in the status you expect it to be when your Zap runs.

API docs for Jira Software Cloud are located here https://docs.atlassian.com/jira/REST/cloud/

Requests can only be made to domains associated by this application.

These params will be URL-encoded and appended to the URL when making the request.

Authentication headers are included automatically

Zapier will apply these optional headers and values to the request in addition to any headers created as part of the authentication mechanism.

Zapier will pass this along raw. If you would like to provide complex JSON, try a "Code by Zapier" step to build the structure and pass it along here. For example, `{"foo": "bar"}` is perfectly valid.

Jira Software Cloud is a bug and issue tracking tool that allows software developers to manage product development. This integration connects to cloud-hosted instances of Jira.

Zapier Automation Platform

By role

By workflow

By company size

Streamline team comms

Drive growth—at scale

By role

Learn more

Get help

Zapier quick-start guide

Developer resources

Jira Software Cloud Integrations

Jira Software Cloud Help & Support

Jira Software Cloud Tutorials

How to use OpenAI to add acceptance criteria to product issues

About Jira Software Cloud

Related categories

Get started for free