You must only install apps that call the Teamwork Graph API in test organizations. Apps calling the Teamwork Graph API require the read:graph:jiraor read:graph:confluence scope, which provides access to Teamwork Graph data across your entire organization. While apps still respect end-user permissions, this scope may grant access to sensitive information. For safety, only install these apps in organizations with test data. Do not install apps using this API in organizations with production data while this feature is in EAP.

Additionally, this EAP has significant limitations. To review the full list of limitations, see Limitations and considerations.

You must be part of this EAP in order to use the Teamwork Graph API. Express interest in joining through this form.

The `JiraWorkItemHasChangedJiraStatus` relationship represents the link between a Jira Work Item and a Jira Work Item status within the Teamwork Graph. It allows you to:
* Track status transitions for Jira Work Items
* Traverse and analyze status change events

Relationship type: Activity

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.

From object types	To object types
Jira Work Item - `ati:cloud:jira:issue`	Jira Work Item Status - `ati:cloud:jira:issue-status`

Cypher

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.

Forward query

Inverse query

GraphQL

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

Params

1
2
{
  "cypherQuery": "MATCH (item:JiraWorkItem {ari: $id})-[:jira_work_item_has_changed_jira_status]->(status:JiraWorkItemStatus) RETURN status",
  "params": {
    "id": "$id"
  }
}

Metadata

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`