Reopen tickets for RMM outages
Use workflows and rules to reopen previously closed tickets for recurring RMM outages. Reopening a ticket preserves the outage history and improves reporting accuracy. When a ticket is reopened, the event is logged in the ticket.
Why reopen a previous ticket
- Preserve historical context
- Reopening a ticket keeps the full history of the outage. This continuity helps identify patterns in recurring outages and avoids splitting the incident across multiple tickets.
- Reduce the number of tickets
- Avoid cluttering the system with duplicate tickets. Reopening ensures the issue is tracked under a single ticket.
- Improve reporting
- Reopened tickets help measure resolution times more accurately. Creating new tickets for the same outage can distort metrics and make it harder to assess the true impact and responsiveness.
Create a workflow rule to update previous tickets
In this scenario, a ticket is reopened and updated when an RMM outage occurs on the same asset, is caused by the same failed check, and is for the same customer on the same day.
Set conditions
- Create a workflow rule for RMM outages.
- In the Condition section, select Previous Ticket - Title.
- Set the operator to equals '='.
- Enter the specific title for the recurring outage. Outage ticket titles are assigned as: <customer name> <asset name> <check name>
- Add another condition: Previous Ticket - Closed Date.
- Set the operator to equals '=' and choose Today as the value.
Define actions
- In the Actions section, choose the Update Previous Ticket action and add it to the workflow.
- Add another action: Set Property.
- Select
next to the Set Property action, choose Ticket Status, and set the value to In Progress. - Save the action.
- Save the rule to apply the new conditions and actions to the workflow.
