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

Track which users reported specific Jira issues
Find all Jira issues that a particular user reported
Traverse and analyze user-issue 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 UserReportsIssue_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_reports_issue]->(issue:JiraIssue) RETURN issue",
  "params": {
    "id": "$id"
  }
}

Inverse Query

GraphQL

1
2
query UserReportsIssue_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_reports_issue]->(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.

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`