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.

• Run on... the following selection options are available:
  • Every ticket change: the trigger will be executed as soon as the ticket changes.
  • Every ticket change in which the ticket is moved to the status: the trigger is executed as soon as the ticket changes its status. The selection of a status that must be present after the change is made from another list. It is important that this status must be newly assigned.
  • Every ticket change where the ticket is in the following status: every change to the ticket leads to the execution of the trigger if the ticket has a certain status. Here, the status can be newly assigned or already existing.
  • Every ticket change through which the following condition is fulfilled: the trigger will be executed the first time that the following condition is fulfilled. This means that a selected ticket field has to change before this trigger runs.
  • Every ticket change due to the following action the trigger will be executed whenever one of the chosen actions is executed.
  • Every ticket change in which the following ticket field is changed: the trigger will be executed whenever the selected ticket field is being changed. Also applies to newly created tickets.

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:

• One trigger for finished tickets, which will start the invoice creation process
• Two report render actions to create the invoice and the email content (see below)
• Two actions:
  • The first action sends an email with the invoice to the ticket owner
  • The second action attaches the invoice to the originating ticket.

To send the invoice, there are two reports that will be rendered:

• the email content
• the actual invoice

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.