Notifications
  • No notifications
View All
?
User -

Reviewing an alert and raising a ticket from it

All guides

Mark alerts reviewed, and turn one into a ticket without retyping the device context.

  1. 1

    Mark an alert reviewed

    Each row has a check-icon button, Mark Reviewed. Once clicked the row shows a tick and the reviewer's first name, and hovering shows who reviewed it and when. Reviewing records that a human has seen the alert — it does not resolve, hide or close anything.

  2. 2

    Clear a backlog in one go

    Mark All Reviewed sets every unreviewed alert in the system as reviewed by you, not just the ones on screen. Use the Reviewed status filter to find them again afterwards.

  3. 3

    Raise a ticket from the alert

    Alerts that have no ticket yet show a + Ticket button. It opens Raise Ticket in a new tab with the site, device, serial, severity and alert text already carried across, so you are not copying identifiers by hand.

  4. 4

    Pick the job type FIRST

    On the Raise Ticket page, choose the Job Type before editing anything else. A job type auto-fills the title, description, priority, asset and SLA — and when the ticket came from an alert, the alert context then overwrites the title and description. Choosing the job type afterwards will wipe what you wrote.

  5. 5

    Confirm the link

    Once the ticket is created, the alert row stops showing + Ticket and shows the ticket number as a green link instead. If it still shows + Ticket, the link did not record and the alert will look untouched to the next person.

Worth knowing

  • The API calls this action "acknowledge" and the interface calls it "review". They are the same thing — one alert, one record of who looked at it.
  • Job types can carry a Fixed SLA, which cannot be changed on the ticket, or a Flexible one you can adjust. The badge next to the selected job type tells you which.