Configuring trigger actions
Under
- Change issue status
- Create issue
- Update fields
- Add issue to active sprint
- Move issue
- Add comment to issue
- Create checklist
- Calculate value
- HTTP request
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.
Creating an issue
You can set up a trigger that will automatically create an issue when certain conditions are met. For example, you can set up a trigger that creates an issue for testing when a programmer implements a new feature and updates the issue status to Resolved.
To set up creation of an issue:
-
Fill in the new issue's template fields:
- Specify the queue where the issue will be automatically created.
- Set issue parameters and click Save.
-
If you want the Tracker robot to be the issue author, select Create as robot. Make sure that the robot has rights for creating issues in the selected queue.
If the option is disabled, the user whose action fired the trigger will be assigned as the issue's author. In this case, the issue will be created only if the user has rights for creating issues in the selected queue.
-
If you want to link the issue that enabled the trigger to the issue created by that trigger, select Link with initial issue.
You can configure automatic creation of multiple issues.
Updating fields
Set one or multiple issue parameters:
-
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
). -
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). -
Set a new value for the parameter.
You can't change the value of the Parent ticket field using an auto action.
Adding an issue to an active sprint
Specify the name of the board with a backlog and sprints where you want to add an issue.
Moving an issue
Select the queue to move your issue to.
The issue will be moved only if the user who ran the trigger has rights for creating issues in the selected queue.
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.
Create a checklist
Create a checklist that will be added to an issue.
The action won't work if the issue already contains a checklist.
To set up a checklist:
-
Click
Add item.
You can add one or more items. -
Enter a description for the item. If necessary, specify the assignee and deadline.
-
Click Save.
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:
-
Set a formula for calculating the value:
- Click sequence like
{{issue.<field_key>}}
.
If the required field is missing from Tracker, you can create one.
Add variable and add a field formula with numeric values. The formula will include a - 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, thetoday()+3d
function returns the date that is three days from now.
- Click sequence like
-
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:
-
Select the HTTP request method.
-
Specify the full URL of the resource to which the request will be sent. For example:
http://example.org/newfolder/newfile
. -
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.
- NoAuth
-
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.
-
Enter the headers and their values.
-
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.