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
Last updated Oct 29, 2025

User assigned issue

The UserAssignedIssue 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: Activity

From object typeTo object type
Identity user - ati:cloud:identity:userJira 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 UserAssignedIssue_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_assigned_issue]->(issue:JiraIssue) RETURN issue",
 "params": {
  "id": "$id"
 }
}

Inverse query

GraphQL
1
2
query UserAssignedIssue_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_assigned_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.

To metadata

Relationship metadata

NameTypeDescription
creatorAriAri (Message)ARI of the user who created the issue.
statusCategoryStatusCategory (Enum)Current status category of the issue.
issueTypeIssueType (Message)Type of the issue.
dueDateLongDue date timestamp for the issue if set.
projectTypeProjectType (Enum)Type of the Jira project containing this issue.
actorAriAri (Message)ARI of the user who performed the assignment action.

Ari

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

NameTypeDescription
valueStringThe ARI string value identifying the user or resource.

IssueType

NameTypeDescription
hierarchyLevelHierarchyLevel (Enum)Hierarchical level of the issue type.
issueTypeNameIssueTypeName (Enum)Name of the issue type.

StatusCategory

NameInternal NameIndexDescription
not-setSTATUS_NOT_SET0Status category has not been set.
undefinedSTATUS_UNDEFINED1Status category is undefined.
newSTATUS_NEW2Issue is new and has not been started.
doneSTATUS_DONE3Issue has been completed.
indeterminateSTATUS_INDETERMINATE4Issue is in progress or has an indeterminate status.

ProjectType

NameInternal NameIndexDescription
not-setTYPE_PROJECT_TYPE_NOT_SET0Project type has not been set.
service_deskTYPE_PROJECT_TYPE_SERVICE_DESK1Service desk project for managing customer support requests.
businessTYPE_PROJECT_TYPE_BUSINESS2Business project for managing business processes and workflows.
softwareTYPE_PROJECT_TYPE_SOFTWARE3Software development project using agile methodologies.
product_discoveryTYPE_PROJECT_TYPE_PRODUCT_DISCOVERY4Product discovery project for researching and validating ideas.
customer_serviceTYPE_PROJECT_TYPE_CUSTOMER_SERVICE5Customer service project for managing support activities.
opsTYPE_PROJECT_TYPE_OPS6Operations project for managing infrastructure and processes.

HierarchyLevel

NameInternal NameIndexDescription
undefinedTYPE_HIERARCHY_LEVEL_NOT_SET0Hierarchy level has not been defined.
subtaskTYPE_HIERARCHY_LEVEL_SUBTASK1Subtask level - smallest unit of work under a parent issue.
standardTYPE_HIERARCHY_LEVEL_STANDARD2Standard level - typical issue like stories, tasks, or bugs.
epicTYPE_HIERARCHY_LEVEL_EPIC3Epic level - large feature or initiative containing multiple issues.
initiativeTYPE_HIERARCHY_LEVEL_INITIATIVE4Initiative level - highest level grouping containing multiple epics.

IssueTypeName

NameInternal NameIndexDescription
not-setTYPE_UNKNOWN0Issue type has not been set or is unknown.
AlertsTYPE_ALERTS2Alert issue type for notifications and warnings.
BugTYPE_BUG4Bug issue type for tracking defects and errors.
EpicTYPE_EPIC10Epic issue type for large features or initiatives.
TaskTYPE_TASK20Task issue type for general work items.
StoryTYPE_STORY30Story issue type for user stories and requirements.
Sub-taskTYPE_SUBTASK40Subtask issue type for breaking down larger work items.
Sub-TaskTYPE_SUBTASK_150Subtask issue type variant for breaking down larger work items.
SubtaskTYPE_SUBTASK_260Subtask issue type variant for breaking down larger work items.
SUBTASKTYPE_SUBTASK_370Subtask issue type variant for breaking down larger work items.

Rate this page: