JCS issue associated support escalation

The Teamwork Graph API is coming soon. The relationship types documented here are indicative of what will be available in the Graph via the Teamwork Graph API. Please note that relationships, their properties, and functionality may change before and during the Early Access Program.

Interested in early access? Express your interest in joining the EAP

The JcsIssueAssociatedSupportEscalation relationship represents the link between a JCS issue and its associated support escalation within the Teamwork Graph. It allows you to:

Retrieve support escalations for a specific JCS issue
Find which JCS issues are associated with a support escalation
Traverse and analyze jcs-escalation relationships

Types

From Object Types	To Object Types
`Jira Issue - ati:cloud:jira:issue`	`Jira Project - ati:cloud:jira:project`
	`Jira Issue - ati:cloud:jira:issue`

Cypher

Forward Query

GraphQL

1
2
query JcsIssueAssociatedSupportEscalation_CypherQuery($cypherQuery: String!, $params: CypherRequestParams) {
  cypherQuery(query: $cypherQuery, params: $params) {
    edges {
      node {
        columns {
          value {
            ... on CypherQueryResultNode {
              id
              data {
                __typename
                ... on JiraProject {
                  id
                }
                ... on JiraIssue {
                  id
                }
              }
            }
          }
        }
      }
    }
  }
}

Params

Note

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.

1
2
{
  "cypherQuery": "MATCH (issue:JiraIssue {ari: $id})-[:jcs_issue_associated_support_escalation]->(project:JiraProject) RETURN project",
  "params": {
    "id": "$id"
  }
}

Inverse Query

GraphQL

1
2
query JcsIssueAssociatedSupportEscalation_CypherQuery($cypherQuery: String!, $params: CypherRequestParams) {
  cypherQuery(query: $cypherQuery, params: $params) {
    edges {
      node {
        columns {
          value {
            ... on CypherQueryResultNode {
              id
              data {
                __typename
                ... on JiraIssue {
                  id
                }
              }
            }
          }
        }
      }
    }
  }
}

Params

Note

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.

1
2
{
  "cypherQuery": "MATCH (issue:JiraIssue)-[:jcs_issue_associated_support_escalation]->(project:JiraProject {ari: $id}) RETURN issue",
  "params": {
    "id": "$id"
  }
}

Metadata

Relationship Metadata

Name	Type	Properties
`SupportEscalationLastUpdated`	`Long`
`creatorAri`	Ari (`Message`)
`status`	EscalationStatus (`Enum`)
`linkType`	EscalationLinkType (`Enum`)

Nested Types

Ari

When filtering by ARI in GraphQL, it will behave as a String rather than a message as shown below.

Name	Type	Properties
`value`	`String`

EscalationStatus

Name	Internal Name	Index
`open`	`OPEN`	`0`
`accepted`	`ACCEPTED`	`100`
`rejected`	`REJECTED`	`110`

EscalationLinkType

Name	Internal Name	Index
`not_set`	`LINK_NOT_SET`	`0`
`new-work-item`	`LINK_TO_NEW_WORK_ITEM`	`100`
`existing-work-item`	`LINK_TO_EXISTING_WORK_ITEM`	`110`