"Automatic actions” are designed to set up specific automation, i.e., to enhance embedded system actions. By means of these actions, you can change issue attributes, move them to another project, add a comment, or create a task. Automatic actions are applied only to primary (custom) requirements - issues, requests, stories, etc. Automatic actions can also address to a certain network address and transmit the required information, i.e., invoke the so-called web hook - link on another server.
Automatic actions are activated when the following events occur:
In addition to this, an automatic action can be linked to the particular transition or state in the lifecycle settings. You must specify a condition when this automatic action is triggered, as well as to specify the required changes to be performed.
Execution order of automatic actions is determined by their numbers. You can change these numbers in the edit form or by dragging rows in the list of actions.
If an employee forgot to log time for the story assigned to him, let us send him a notification about the necessity to do it.
To do it, create a recurring action, e.g., at the end of the working day, and use it as a trigger for automatic action.
Select "Add comment" as action and enter the following text:
This comment will be added to the story, and the assignee will be explicitly notified about the necessity to log time.
You can send e-mail notification to the particular address or to system users. To do this, fill the fields on the corresponding tab: