The Task Planner trigger Ticket Changed will run the task as soon as a ticket has been changed by an edit. Here, it can be selected to which changes the trigger is to react. The placeholder Ticket-ID
of the ticket that caused this trigger to be executed will be passed to the subsequent jobs and actions.
AND
and OR
.<
, >
, ==
, !=
Note: If this trigger is called for a given ticket more than 10 times in a minute, it will enter a cooldown phase of 5 minutes (limited to this specific ticket) to avoid an endless loop. Check your tasks' execution history for more information on how an endless loop might have happened. For example, if you set up your task to trigger on ticket changes and then change tickets in your task, it could create a loop like this.
Whenever a ticket reaches the Finished
(Beended
) status, an invoice should be created. To do this, the trigger Ticket Changed
can be set up with the corresponding status. As an action, the creation of a report with the prepared invoice is selected and the ticket ID is passed as a parameter.
The report can then be saved or forwarded by email.
For this exact example, there is a template in the Task Planner that can be used and extended. When creating a new Task Planner task, select the When the ticket is closed, send the invoice template.
Note: You have to have the Attachments and Render Reporting plugins enabled or the template will not be in the list.
The task consists of:
To send the invoice, there are two reports that will be rendered:
Since i-net Clear Reports support rendering reports into email content, using simplified HTML, you can design your email as required and add the [jobresult]
to the Email-Action {owner.email}
placeholder to use the ticket owners' email.
Provides placeholders to other task planner components.