Add a Trigger to an Operation

To add a trigger to an newly created operation, click Add Trigger next to the operation on the "Manage Operations" page.

The "Add Trigger" dialog is displayed.

The input parameters for the trigger depend on the selected trigger type. The following trigger types are available:

Manual

Users can select this operation in the Publish Issue action (via the Actions menu of an issue).

  • Name: Enter a name for this trigger. If left empty, the trigger text will be used.

  • Project: Select the allowed projects. If nothing is selected this operation is available in all projects.

  • Select the allowed issue types. If nothing is selected this operation is available for all issue types.

  • Status: Select the allowed statuses. If nothing is selected this operation is available in any status.

  • JQL: Enter a JQL filter for this operation (e.g. assignee = currentUser()).
  • Groups: Select the allowed user groups. If nothing is selected this operation can be triggered by all users.

REST API

This operation can be triggered by a REST call.

The available inputs are the same as for the Manual trigger.

Post Function

This operation can be selected in the Publish Issue Using Operation post function.

  • Name: Enter a name for this trigger. If left empty, the trigger text will be used.

You can configure a JQL filter in the Publish Issue Using Operation post function.

Event

Automatically execute the operation based on issue events.

  • Name: Enter a name for this trigger. If left empty, the trigger text will be used.
  • Event Types: Select the event types that should trigger this operation.

  • Project: Select the allowed projects. If nothing is selected this operation is available in all projects.

  • Select the allowed issue types. If nothing is selected this operation is available for all issue types.

  • Status: Select the allowed statuses. If nothing is selected this operation is available in any status.

  • JQL: Enter a JQL filter for this operation (e.g. assignee = currentUser()).

  • Ignored Users: The operation will not be executed if triggered by one of the selected users.

Either a project or issue type or status is required.

If an operation has multiple Event triggers and more than one of them match a given issue event, the operation is performed once for each matching trigger.

This behavior might change in the future.

You can have a maximum of 100 event triggers on all active operations. An operation is considered active if it is enabled and has at least one trigger and one step.