2 minute readApplies to: v3

How to add links to an external ticketing system

Using this setting, allows you to turn the ticket field on a SquaredUp Alert drilldown into a link to a ticket in your external service desk or ticketing system. This is useful if you have a separate ticketing/service desk system that has a web interface.


The ticket hyperlink is configured through a setting stored in scom.json.

On the Windows Server where SquaredUp is installed:

  1. Navigate to the following directory: C:\inetpub\wwwroot\squaredupv3\User\Configuration.
  2. Open the scom.json file (you may need to open Notepad as an administrator).
  3. Add the following line and replace with the desired template. You may not need the id= depending on your particular service desk URLs. {{ticketId}} is automatically replaced with the value of the ticket ID field in the Alert.

    "ticket-template": "http://my-ticketing-system/id={{ticketId}}"

  4. You may also need to add a comma at the end of the previous line, if there are multiple settings in the file.

Linking to an alert

Once the template URL is setup, any alerts with a ticket ID will display a link.

  1. Drilldown into any alert within SquaredUp.
  2. Select the ticket button near the top right of the page.
  3. Enter the desired ticket ID
  4. Click update.

You'll now see the ticket ID displayed alongside the alert name. Clicking this tag will open a new window to your external ticketing system / service desk.


Using the curly brace syntax, e.g. {{variable}} you can include different variables in the URL template. In the example above we used {{ticketId}}.

  • classId
  • customField1
  • customField2
  • customField3
  • customField4
  • customField5
  • customField6
  • customField7
  • customField8
  • customField9
  • customField10
  • description
  • id
  • isMonitorAlert
  • lastModified
  • lastModifiedBy
  • monitoringObjectDisplayName
  • monitoringObjectId
  • monitoringObjectPath
  • name
  • owner
  • priority
  • problemId
  • repeatCount
  • resolutionState
  • resolutionStateName
  • resolvedBy
  • ruleId
  • severity
  • ticketId
  • timeRaised
  • timeResolved
  • type

How to use criteria when scoping Alerts

Squared Up Ltd. (c) 2020Report an issue with this article