Configure trigger actions

Configure one or more actions in the Trigger action block by clicking Add action:

  1. Change issue status
  2. Change field values
  3. Add comment
  4. Calculating values
  5. Move issue
  6. Create an issue
  7. HTTP request

Change issue status

Set a new issue status. Available statuses are determined by your workflow settings.

Change field values

Set new values for one or more fields:

  1. Click Select fields and specify the field.
  2. Choose an action:
    Action Description
    Set value Assigns the set value to a field
    Clear field Clears the field value.
    Add to the list Add one more field value (for fields that can contain multiple elements).
    Remove from list Remove one of the field values (for fields that can contain multiple elements).
  3. Enter a new field value.

Add comment

Enter the comment you wish to add to the issue.

You can also enter issue field values in your comment. To do this, click Add variable and select one or more values. You will see a sequence in the Comment field in the format {{issues.field_ID}}.

Calculating values

You can set up a special field whose values are calculated automatically based on values entered in other fields. For example, you can automatically calculate the value of a metric.

To automatically calculate the value of a field:

  1. Add the trigger action Calculate value.
  2. Specify the formula to calculate the value by:
    • Click Add variable and add a field formula with numeric values. The formula will include a sequence like {{issue.field_ID}}.

      If Tracker doesn't have the needed field, you can create one.

    • You can use mathematical symbols for addition +, subtraction -, multiplication *, and division /.
    • Use brackets (parentheses) to prioritize certain operations over others.
  3. Click Choose field and set the field you want to put the calculated value into.
    Note. The field value is rounded up to an integer.
  4. Set a condition that will trigger the calculation of the field value in the Trigger condition section. We recommend using the event Formula fields changed. You can also set any condition appropriate for your workflow.

Move issue

Specify the queue to move the issue to.

Create an issue

You can set a trigger that automatically creates an issue when all specified conditions are met. For example, you can create a trigger that creates an issue for beta testing when a programmer implements a new feature and updates the issue status to “Resolved”.

To configure issue creation:

  1. Add the trigger action Create issue.
  2. Click Fill in fields.
  3. In the Issue creation window:
    1. Specify the queue to create the issue in.
    2. Set issue parameters and click Save.
  4. If you want the Tracker robot to be the issue reporter, enable the option Let the robot create issues. Make sure the robot has permission to create issues in the queue.

    If this option is disabled, the user who triggered the action becomes the issue reporter instead.

  5. If you want to link the issue that enabled the trigger to the issue created by that trigger, turn on the option Link to issue that enabled the trigger

HTTP request

If you want the trigger to send an HTTP request:

  1. Select the HTTP request method.

  2. Specify the full address of the website that will be used to send the request. For example:

  3. Choose your login method:

    • NoAuth

      No authorization.

    • Basic

      Requires a username and a password.

    • OAuth 2.0

      Requires a token, an auth header, and a token type.

    All authorization data (login, password, token, authorization header, token type) is sent to the according fields and you don't need to specify any of it again in the headers.

  4. Enter request body.

    You can insert field values and user variables in your request body (see below). To do this, click { } to the right of the field and choose the name for the field or value. The request body will include a sequence like {{variable_name}}.

    Note. You can also add variables to the website address or header value.
  5. Enter headers and their values.

  6. You can add more variables to your request body or header if needed. For example, you can add an authentication key or any other private information.
    Note. After the trigger is saved, the value of the variable is hidden and can't be viewed.

To view examples for setting up HTTP requests that send notifications to Slack and Telegram from Tracker, see Messenger integration.