Issue has assignee

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

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

Links Jira issues to their assigned users, establishing responsibility and ownership for issue resolution Relationship type: Canonical

From object types	To object types
Jira Issue - `ati:cloud:jira:issue`	Identity User - `ati:cloud:identity:user`

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

GraphQL

1
2
query IssueHasAssignee_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

1
2
{
  "cypherQuery": "MATCH (issue:JiraIssue {ari: $id})-[:issue_has_assignee]->(user:IdentityUser) RETURN user",
  "params": {
    "id": "$id"
  }
}

Inverse query

GraphQL

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

Params

1
2
{
  "cypherQuery": "MATCH (issue:JiraIssue)-[:issue_has_assignee]->(user:IdentityUser {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.

From Metadata

Name	Type	Properties
`statusAri`	Ari (`Message`)
`dueDate`	`Long`

To Metadata

Name	Type	Properties
`statusAri`	Ari (`Message`)
`dueDate`	`Long`

Relationship Metadata

Name	Type	Properties
`dueDate`	`Long`
`statusCategory`	StatusCategory (`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`

StatusCategory

Name	Internal Name	Index
`undefined`	`CATEGORY_UNDEFINED`	`0`
`new`	`CATEGORY_TO_DO`	`2`
`done`	`CATEGORY_DONE`	`3`
`indeterminate`	`CATEGORY_IN_PROGRESS`	`4`