Developer
Get Support
Sign in
Get Support
Sign in
DOCUMENTATION
Cloud
Data Center
Resources
Sign in
Sign in
DOCUMENTATION
Cloud
Data Center
Resources
Sign in
Relationship types
Last updated Nov 25, 2025

Atlassian user assigned Jira work item

The AtlassianUserAssignedJiraWorkItem relationship represents the link between an Identity user and a Jira issue within the Teamwork Graph. It allows you to:

  • View all Jira issues currently assigned to a specific user
  • Identify who is responsible for resolving a particular Jira issue
  • Traverse and analyze user-issue relationships

Relationship type: Canonical

From object typesTo object types
Identity User - ati:cloud:identity:userJira Issue - ati:cloud:jira:issue

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 AtlassianUserAssignedJiraWorkItem_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 (user:IdentityUser {ari: $id})-[:atlassian_user_assigned_jira_work_item]->(issue:JiraIssue) RETURN issue",
  "params": {
    "id": "$id"
  }
}

Inverse query

GraphQL
1
2
query AtlassianUserAssignedJiraWorkItem_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 (user:IdentityUser)-[:atlassian_user_assigned_jira_work_item]->(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

Relationship Metadata

NameTypeProperties
creatorAriAri (Message)
statusCategoryStatusCategory (Enum)
issueTypeIssueType (Message)
dueDateLong
projectTypeProjectType (Enum)
actorAriAri (Message)

Nested Types

Ari

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

NameTypeProperties
valueString

IssueType

NameTypeProperties
hierarchyLevelHierarchyLevel (Enum)
issueTypeNameIssueTypeName (Enum)

StatusCategory

NameInternal NameIndex
not-setSTATUS_NOT_SET0
undefinedSTATUS_UNDEFINED1
newSTATUS_NEW2
doneSTATUS_DONE3
indeterminateSTATUS_INDETERMINATE4

ProjectType

NameInternal NameIndex
not-setTYPE_PROJECT_TYPE_NOT_SET0
service_deskTYPE_PROJECT_TYPE_SERVICE_DESK1
businessTYPE_PROJECT_TYPE_BUSINESS2
softwareTYPE_PROJECT_TYPE_SOFTWARE3
product_discoveryTYPE_PROJECT_TYPE_PRODUCT_DISCOVERY4
customer_serviceTYPE_PROJECT_TYPE_CUSTOMER_SERVICE5
opsTYPE_PROJECT_TYPE_OPS6

HierarchyLevel

NameInternal NameIndex
undefinedTYPE_HIERARCHY_LEVEL_NOT_SET0
subtaskTYPE_HIERARCHY_LEVEL_SUBTASK1
standardTYPE_HIERARCHY_LEVEL_STANDARD2
epicTYPE_HIERARCHY_LEVEL_EPIC3
initiativeTYPE_HIERARCHY_LEVEL_INITIATIVE4

IssueTypeName

NameInternal NameIndex
not-setTYPE_UNKNOWN0
AlertsTYPE_ALERTS2
BugTYPE_BUG4
EpicTYPE_EPIC10
TaskTYPE_TASK20
StoryTYPE_STORY30
Sub-taskTYPE_SUBTASK40
Sub-TaskTYPE_SUBTASK_150
SubtaskTYPE_SUBTASK_260
SUBTASKTYPE_SUBTASK_370

Rate this page: