Fortunately, restoring the template is easy enough. When your template is misbehaving, it’s sometimes best to start with a clean template. While working on your template, it might be helpfult to either restore to the default template or test your current template against an existing ticket. ![]() These suggestions are based on the subject of the ticket that is submitted. You can include this in your template with the following variables: ticket.suggested_kb_articles ![]() You can automatically suggest related knowledge base articles that you have chosen to share with your end users through the user portal (for more information on this feature, see this doc). You can add a list of the cc’d users of a ticket by inserting the following code to your template: Displaying CC’d usersīecause Spiceworks only shows the email address of the ticket recipient in the notification email, you might want to include a list of all users who are cc’d to the ticket so your users will know. Some of the most commonly changed aspects of the templates are listed, with code examples, below. That point it’s nice to have a few pointers or have the option to restore to the default template. While customizing you can be left scratching your head if a template doesn’t quite look like you’d expect. ![]() Within the Spiceworks On-Prem Help Desk you can customize the outgoing ticket notification emails. Customizing email notifications Applies to: On-Prem Help Desk
0 Comments
Leave a Reply. |