Issue has changed priority

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 IssueHasChangedPriority relationship represents the link between a Jira issue and a Jira issue priority within the Teamwork Graph. It allows you to:

Track priority changes for specific Jira issues
Traverse and analyze issue priority change events

TTL

30 days

The TTL (Time To Live) specifies the retention period for relationship data, determining how far back in time the relationship remains queryable.

Types

From Object Types	To Object Types
`Jira Issue - ati:cloud:jira:issue`	`Jira Issue Priority - ati:cloud:jira:priority`

Cypher

Forward Query

GraphQL

1
2
query IssueHasChangedPriority_CypherQuery($cypherQuery: String!, $params: CypherRequestParams) {
  cypherQuery(query: $cypherQuery, params: $params) {
    edges {
      node {
        columns {
          value {
            ... on CypherQueryResultNode {
              id
              data {
                __typename
                ... on JiraPriority {
                  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})-[:issue_has_changed_priority]->(priority:JiraIssuePriority) RETURN priority",
  "params": {
    "id": "$id"
  }
}

Inverse Query

GraphQL

1
2
query IssueHasChangedPriority_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)-[:issue_has_changed_priority]->(priority:JiraIssuePriority {ari: $id}) RETURN issue",
  "params": {
    "id": "$id"
  }
}

Metadata

This relationship is not indexed, you will not be able to filter by this metadata when querying the relationship.

Relationship Metadata

Name	Type	Properties
`actorAri`	Ari (`Message`)

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`