User assigned PIR

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 UserAssignedPir relationship represents the link between an Identity user and a Jira issue representing a post-incident review within the Teamwork Graph. It allows you to:

View all post-incident reviews currently assigned to a specific user
Identify who is responsible for completing a particular post-incident review
Traverse and analyze user-pir relationships

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 UserAssignedPir_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_assigned_pir]->(issue:JiraIssue) RETURN issue",
  "params": {
    "id": "$id"
  }
}

Inverse Query

GraphQL

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

Metadata

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

To Metadata

Name	Type	Properties
`statusAri`	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`