User viewed Jira issue

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 UserViewedJiraIssue relationship represents the link between an Identity user and a Jira issue they viewed within the Teamwork Graph. It allows you to:

Track which users have viewed specific Jira issues
Find all Jira issues that a user has viewed
Traverse and analyze user-issue relationships

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
`Identity User - ati:cloud:identity:user`	`Jira Issue - ati:cloud:jira:issue`

Cypher

Forward Query

GraphQL

1
2
query UserViewedJiraIssue_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 (user:IdentityUser {ari: $id})-[:user_viewed_jira_issue]->(issue:JiraIssue) RETURN issue",
  "params": {
    "id": "$id"
  }
}

Inverse Query

GraphQL

1
2
query UserViewedJiraIssue_CypherQuery($cypherQuery: String!, $params: CypherRequestParams) {
  cypherQuery(query: $cypherQuery, params: $params) {
    edges {
      node {
        columns {
          value {
            ... on CypherQueryResultNode {
              id
              data {
                __typename
                ... on AtlassianAccountUser {
                  id
                }
                ... on CustomerUser {
                  id
                }
                ... on AppUser {
                  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 (user:IdentityUser)-[:user_viewed_jira_issue]->(issue:JiraIssue {ari: $id}) RETURN user",
  "params": {
    "id": "$id"
  }
}