The most recent content from our members.
Allow automation rules to run only when a ticket is resolved by an agent or requester. Or allow to run based on Resolved by or Resolution code fields.
This could be a little risky, but it would be nice to allow the merge function in automation rule actions.
I have been adjusting roles and automation rules trying to find a good way to restrict changes to the priority of a ticket unless you are a member of a specific group. We want changes to priority changes to only be allowed by a small group of agents or managers. Does anyone know of a way to do this?
I have automation rules that seem to have stopped running consistently. Is there a way to trigger them manually for testing?
It would be better if we able to write multiple keywords in the automation workflow condition so that single workflow should be use to perform multiple operations.
I would love to see a Time Based Condition in Automations so that we can only have certain automations run on specific days during specific times. This would allow us to have Critical tickets send emails out for afterhours support and not during the work day. Couple of screen shots below for an example. allow automation to…
I would like to see the option below separated. One switch for resolved, and one switch for closed. Closed should be the absolute end of the life of an incident, whereas users should be able to respond to a resolved ticket if its not actually resolved, and then it should be reopened for additional work. It would be nice to…
We currently have a rule which sets our tickets to "Customer Responded" state if the requester comments on the ticket. However, when someone who is CC'd on the ticket responds, this change does not happen. Selecting CC'd users is not currently an option in the automation rules.
Currently the only automation option to add information in the ticket is to Append or Prepend the original request details. Feature request is to have the option of adding a Public or Hidden comment to the ticket inline with the thread. To use as automatic notes for technicians or automatic responses to the requester.
When forwarding a ticket from one Service Provider to another in ESM, using an automation in the receiving Service Provider to auto assign to a queue or agent is currently not supported. Please allow this function so forwarded tickets can be auto assigned without manual intervention.
It looks like you're new here. Sign in or register to get started.