Automatic issue updates in Tracker

With auto actions, you can automatically update issues based on the conditions you set in filters. Issues will be updated as scheduled. For example, you can invite a lead to comment if the issue hasn't been updated for a long time.

To set up auto actions, the Queue management access rights are required.

When triggered, the auto action processes only the first 100 issues that meet the specified criteria. Other issues will be processed the next time the auto action is triggered.

Configuring automatic issue updates

  1. In the left-hand panel, click  Queues and select a queue.

  2. In the top right corner of the queue page, click  Queue settings.

  3. Select Automation in the left-hand panel.

  4. In the top right corner, click Create → Auto action.

  5. Select Issue update as the type of auto action.

  6. Set the name for the auto action.
    You can add a description below the name.

  7. Set the  Trigger schedule, which is the interval of automatic issue update in hours or days.
    To track issue updates, enable the Send a notification every time the trigger fires option.

  8. Select the issues to apply the auto action to:

    • To have the auto action triggered for issues whose parameters match specific values, select the When the issue meets the condition mode. You can add multiple conditions. The auto action will trigger if all the conditions hold at the same time.
    • To have the auto action triggered for issues that meet the filter criteria, select the When the issue matches the QL query mode and set the conditions in the line using the query language.

  9. Under  Perform actions, set one or more actions on the issue.

  10. To save an auto action, click Create auto action.

The new automation will appear in the list in a few seconds after being added.

Configuring actions

Under  Perform actions, set up one or more actions:

Changing issue status

Set a new issue status. Available statuses may vary depending on the workflow settings.

Automations are performed by a service robot named yndx-tracker-cnt-robot@. To enable the robot to update issue statuses:

  • If certain conditions are set up for status transitions and they restrict user permissions to change a status, add the yndx-tracker-cnt-robot@ robot to the list of users.

  • If you set up a transition screen for a status update, make sure it does not have required fields.

Updating fields

Set one or multiple issue parameters:

  1. Click  Add parameter and select an issue parameter.

    To find a local queue field, enter the key of the queue where you want to set up an automation and a period before the field name (for example, DEVS.Tester).

  2. Select an action:

    Action Description
    Set value Specify the parameter value.
    Clear field Delete a parameter value.
    Add to list Add another parameter value (for parameters with multiple values).
    Remove from list Remove a parameter value (for parameters with multiple values).

  3. Set a new value for the parameter.

You can't change the value of the Parent ticket field using an auto action.

Adding comments to issues

Write the comment text that will be added to an issue.

You can insert values of issue fields into the comment text. To do this, click  Variables and select one or more values. The comment field will show a sequence like {{issue.<field_key>}}.

The comment is sent on behalf of the user who activates the trigger. If you want a robot to appear as the comment author, enable the Send as robot option.

Calculating a value

You can set up a special field whose values are calculated automatically based on values entered in other fields.

To calculate the field value automatically:

  1. Set a formula for calculating the value:

    • Click  Add variable and add a field formula with numeric values. The formula will include a sequence like {{issue.<field_key>}}.
      If the required field is missing from Tracker, you can create one.
    • You can use mathematical symbols for addition +, subtraction -, multiplication *, and division /.
    • To set the priority of operations, use parentheses.
    • To calculate values for date fields, you can use expressions with the today() function. For example, the today()+3d function returns the date that is three days from now.

  2. Click Select a field and set the field you want to put the calculated value into.

    If the field supports only integer values, the value will be rounded.

For an example of implementing the function, see Adding the current date to the field.

HTTP request

You can use HTTP requests to access the API of other services and set up integrations with them.

To send an HTTP request whenever the automation is triggered:

  1. Select the HTTP request method.

  2. Specify the full URL of the resource to which the request will be sent. For example: http://example.org/newfolder/newfile.

  3. Choose the authorization method:

    • NoAuth
      No authorization.
    • Basic
      You are prompted to enter your username and password.
    • OAuth 2.0
      You are prompted to enter a token, authorization header, and token type.

    The authorization data (username, password, token, authorization header, token type) are transmitted in relevant fields and don't require to be re-entered in headers.

  4. Enter the request body.

    You can add issue field values or custom variables to the request body. To do this, click to the right of the field and choose the name for the field or value. The request body will include the {{<variable_name>}} sequence.

    You can also use variables in the resource URL and header value.

  5. Enter the headers and their values.

  6. Add new variables if you need them in the request body or headers. For example, you can add an authentication key or other secret information.

    When you save the trigger, the variable's value is hidden, and you can't look it up later.

When the automation is triggered, Tracker sends an HTTP request. The response can be any HTTP status code.

If no response is received within 10 seconds, or if the response contains code 500, the request will be resent. Each request will be retried up to 5 times, with the delay between attempts increasing exponentially from 10 seconds.

Sample HTTP request settings

Viewing the history of triggered auto actions

To see when an auto action was triggered and its outcome, hover over it in the list of automations and click → History of triggers.

You'll see the list of triggered auto actions in the right panel. For each run, you'll find this information:

  • Start time.

  • The number of issues handled and the total number of issues that meet the condition triggering the auto action.

    To view handled issues, click the line with the run info.

  • Issue handling progress (if it's not completed) or result.

Previous
Examples
Next
Scheduled issue creation