The email address of the user you're adding.

If the user is not on your Guru team, should we invite them?

The group you're adding the user to.

If a group with this name does not exist, should we create it?

The email address of the user you're inviting.

An optional message to include in the invite email (note: invite emails may be disabled, you can check here https://app.getguru.com/settings/email-preferences)

An optional group to add the user to.

The email address of the user you're removing from your team.

The ORDER BY keyword is not allowed in your query. Learn more about JQL.

This Trigger does not use one of your App Connections between Jira and Zapier. Instead, Zapier uses the fields below to connect to your Jira account and adds a Jira webhook that triggers this Zap.

Your Jira account must have the "Administer Jira" global permission.

You can create an API token here.

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.

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).

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

Determines which App Extensions will appear in the dropdown below.

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

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

For example, 100 means we'll trigger when the team reaches 100 cards, 200 cards, 300, etc.

Card ID is in the format of xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. Make sure you have access to this Guru card

The email address of the user.

The group to remove them from.

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

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

This Trigger does not use one of your App Connections between Jira and Zapier. Instead, Zapier uses the fields below to connect to your Jira account and adds a Jira webhook that triggers this Zap.

Your Jira account must have the "Administer Jira" global permission.

You can create an API token here.

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.

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 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.

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).