Jira web triggers are configured to monitor a Jira instance for events.

Overview

The Jira web trigger listens for specific events in a Jira instance. When the events occur in the Jira instance, the trigger initiates the configured automation workflow.

Authentication

The Jira web triggers use client secret for configuring OAuth connection and to authenticate user identity and the received events that the trigger is listening to. The client secret prevents unauthorized users from accessing the incoming Jira data to create and trigger automation.

For information about generating and managing client secrets, see Enabling OAuth 2.0 section in OAuth 2.0 (3LO) apps.

You can store this client secret in the Credential Vault. For information about storing and maintaining credentials in Credential Vault, see Credentials and lockers in the Credential Vault.

See Create OAuth connection for creating and configuring an OAuth connection.

Note: Jira web triggers support only one subscription account.

Supported events

The Jira web triggers support the following events:

Events Description
Issue created When an issue is created in Jira instance.
Issue updated When an existing issue is updated in Jira instance.
Issue deleted When an issue is deleted from Jira instance.
Comment created When a comment is added in Jira instance.
Comment updated When an existing comment is updated in Jira instance.
Comment deleted When a comment is deleted in Jira instance.

Prerequisites

Ensure that the following prerequisites are met:

  • A Bot Creator or Citizen Developer license.
  • View my bots and EVENT TRIGGERS permissions.
  • Check in and Check out permission for the folders in which the automation is located.
  • A Jira client secret.
  • An active OAuth connection for the Jira instance.

Settings

The following settings are available for Jira web triggers:

Listen to event
Select one or more events that the trigger must monitor.
Filter criteria (optional)
Enter a JQL query to monitor specific Jira issues. You can enter a JQL query that is already defined in the Jira instance or enter a new JQL query directly. For more information about building a JQL query, see Use advanced search with Jira Query Language (JQL).

For example: Enter project in (ABC) and status in ("In Progress", "To Do") to search for issues that are in In Progress or To Do status in a project named ABC.

Control room OAuth connection
Use the Pick option, and follow the prompts in the Pick an OAuth connection modal to select the OAuth connection for the Jira instance.
Client secret to verify event response
Use the Client secret to verify event response option to select the client secret for authentication. Select one of the following options:
  • Credential: Use the Choose option and follow the prompts in the Pick a credential modal to select the Jira client secret saved in the Credential Vault.
  • Insecure string: Enter the client secret directly in the input field.
Response (optional)
Use the Response option to save the trigger response data. You can select an existing variable or create a new variable. Only Record variable type is supported.