Open for Voting

Automation rule that can change the requestor of an incident?

We used to use Spiceworks for our I.T. ticketing system and one of the things we liked about it was the ability to email the ticket with commands in the body of the email to do certain tasks.  For example we could reply to a ticket via email with the command "#close" and it would close the ticket.  We've reproduced some of this functionality with automations using the "update record" actions.  We're able to close tickets and assign tickets to our selves if we use keywords in an email reply to the ticket.

A functionality we haven't been able to reproduce is an email reply that can change the requestor.  In Spiceworks we would use this with emails a user would send directly to one of us in the IT department instead of going through the ticketing system like they're supposed to.  We would just forward the ticket to the ticketing system with a command "#created by <email address>".  The Update Record action does not list "requestor" as one of the choices that can be updated on an incident via automations.

  • Oh and if anyone else has accomplished this feat^, please let me know. I would be very appreciative.

  • We're trying to integrate Zabbix with Solarwinds so that when an alert is generated in Zabbix, it generates a ticket in Solarwinds but the problem is that in order to create a JSON web token in solarwinds, you have to be an administrative user which requires a license so we are using our personal tokens but when the ticket is created, the requester is our personal account. I wanted to use an automation rule to look for a keyword and update the ticket requester to "Zabbix" but alas, requester is not an option. Ughhhh.