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

Relationship type: Canonical

From object type	To object type
Identity user - `ati:cloud:identity:user`	Jira issue - `ati:cloud:jira:issue`

Cypher

We recommend using parameterized Cypher queries rather than placing parameters directly in the query string. This helps improve performance.

Forward query

GraphQL

1
2
query UserReportsIssue_CypherQuery($cypherQuery: String!, $params: JSON!) {
 graphStore @optIn(to: ["GraphStore", "GraphStoreCypherQueryV2"]) {
  cypherQueryV2(query: $cypherQuery, params: $params) {
   edges {
    node {
     columns {
      key
      value {. on GraphStoreCypherQueryV2NodeList {
        nodes {
         data {. on JiraIssue {
           id
          }
         }
        }
       }. on GraphStoreCypherQueryV2AriNode {
        data {. on JiraIssue {
          id
         }
        }
       }. on GraphStoreCypherQueryV2BooleanObject {
        bool_val: value
       }. on GraphStoreCypherQueryV2IntObject {
        int_val: value
       }. on GraphStoreCypherQueryV2FloatObject {
        float_val: value
       }. on GraphStoreCypherQueryV2StringObject {
        str_val: value
       }
      }
     }
    }
   }
  }
 }
}

Params

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: JSON!) {
 graphStore @optIn(to: ["GraphStore", "GraphStoreCypherQueryV2"]) {
  cypherQueryV2(query: $cypherQuery, params: $params) {
   edges {
    node {
     columns {
      key
      value {. on GraphStoreCypherQueryV2NodeList {
        nodes {
         data {. on AtlassianAccountUser {
           id
          }. on CustomerUser {
           id
          }. on AppUser {
           id
          }
         }
        }
       }. on GraphStoreCypherQueryV2AriNode {
        data {. on AtlassianAccountUser {
          id
         }. on CustomerUser {
          id
         }. on AppUser {
          id
         }
        }
       }. on GraphStoreCypherQueryV2BooleanObject {
        bool_val: value
       }. on GraphStoreCypherQueryV2IntObject {
        int_val: value
       }. on GraphStoreCypherQueryV2FloatObject {
        float_val: value
       }. on GraphStoreCypherQueryV2StringObject {
        str_val: value
       }
      }
     }
    }
   }
  }
 }
}

Params

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	Description
`statusAri`	Ari (`Message`)	ARI of the user's current status or state.
`dueDate`	`Long`	Due date timestamp if applicable to the user.

To metadata

Name	Type	Description
`statusAri`	Ari (`Message`)	ARI of the current status of the issue.
`dueDate`	`Long`	Due date timestamp for the issue if set.

Relationship metadata

Name	Type	Description
`dueDate`	`Long`	Due date timestamp for the reported issue.
`statusCategory`	StatusCategory (`Enum`)	Status category of the reported issue.

Ari

When filtering by ARI in GraphQL, it will behave as a String rather than a message as shown below.

Name	Type	Description
`value`	`String`	The ARI string value identifying the user or resource.

StatusCategory

Name	Internal Name	Index	Description
`undefined`	`CATEGORY_UNDEFINED`	`0`	Status category is undefined or not set.
`new`	`CATEGORY_TO_DO`	`2`	Issue is new and in the To Do category.
`done`	`CATEGORY_DONE`	`3`	Issue has been completed and is done.
`indeterminate`	`CATEGORY_IN_PROGRESS`	`4`	Issue is in progress or has an indeterminate status.