Last updated Oct 12, 2026

JSM incident links external service

The Teamwork Graph API is available through Forge's Preview release phase.

Preview features are available to all users and receive the same level of support as generally available features. Schemas, fields, and behavior may still change before general availability (GA), and breaking changes are subject to a minimum 1-month deprecation notice, announced in the Teamwork Graph changelog.

To review the current limitations, see Limitations and considerations.

To share feedback or report an issue, visit the Atlassian developer community.

The JsmIncidentLinksExternalService relationship represents the link between a service and the incidents that impact it. It allows you to:

Retrieve incidents that impact a specific service
Find all services affected by a specific incident
Track the blast radius and impact scope of incidents on service infrastructure

Relationship type: Canonical

From object types	To object types
Jira work item - `ati:cloud:jira:issue`	External service - `ati:cloud:graph:service`

Cypher

We recommend sending parameterized Cypher queries as below instead of embedding the parameters directly in the query string. This approach will help ensure better performance.

Forward query

Inverse query

GraphQL

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
query JsmIncidentLinksExternalService_CypherQuery($cypherQuery: String!, $params: CypherRequestParams) {
  cypherQuery(query: $cypherQuery, params: $params) {
    edges {
      node {
        columns {
          value {
            ... on CypherQueryResultNode {
              id
              data {
                __typename
                ... on ExternalService {
                  id
                }
              }
            }
          }
        }
      }
    }
  }
}

Params

1
2
3
4
5
6
7
{
  "cypherQuery": "MATCH (item:JiraWorkItem {ari: $id})-[:jsm_incident_links_external_service]->(service:ExternalService) RETURN service",
  "params": {
    "id": "$id"
  }
}