You must only install apps that call the Teamwork Graph API in test organizations. Apps calling the Teamwork Graph API require the read:graph:jiraor read:graph:confluence scope, which provides access to Teamwork Graph data across your entire organization. While apps still respect end-user permissions, this scope may grant access to sensitive information. For safety, only install these apps in organizations with test data unless you have an approved path to production.

Additionally, this EAP has significant limitations. To review the full list of limitations, see Limitations and considerations.

You must be part of this EAP in order to use the Teamwork Graph API. Express interest in joining through this form.

This relationship represents the link between an IdentityUser and a recommendation they dismissed on the Jira For You page.
Category of each dismissal is modelled in metadata as a list to allow users to dismiss the same entity (e.g. JiraIssue) across multiple categories independently.

Relationship type: Activity

From object types	To object types
Atlassian user - `ati:cloud:identity:user`	Atlassian team - `ati:cloud:identity:team`
	External pull request - `ati:cloud:jira:pull-request, ati:cloud:graph:pull-request`
	Jira space - `ati:cloud:jira:project`
	Jira work item - `ati:cloud:jira:issue`
	Jira work item comment - `ati:cloud:jira:issue-comment`

Cypher

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

Inverse query

GraphQL

1
2
query AtlassianUserDismissedJiraForYouRecommendationEntity_CypherQuery($cypherQuery: String!, $params: CypherRequestParams) {
  cypherQuery(query: $cypherQuery, params: $params) {
    edges {
      node {
        columns {
          value {
            ... on CypherQueryResultNode {
              id
              data {
                __typename
                ... on JiraWorkItem {
                  id
                }
                ... on JiraSpace {
                  id
                }
                ... on JiraWorkItemComment {
                  id
                }
                ... on AtlassianTeam {
                  id
                }
                ... on ExternalPullRequest {
                  id
                }
              }
            }
          }
        }
      }
    }
  }
}

Params

1
2
{
  "cypherQuery": "MATCH (user:AtlassianUser {ari: $id})-[:atlassian_user_dismissed_jira_for_you_recommendation_entity]->(item:JiraWorkItem) RETURN item",
  "params": {
    "id": "$id"
  }
}

Metadata

Relationship Metadata

Name	Type	Properties
`dismissedCategories`	CategoryDismissal (`Message`)	`repeated`

Nested Types

CategoryDismissal

Name	Type	Properties
`category`	RecommendationCategory (`Enum`)

RecommendationCategory

Name	Internal Name	Index
`NOT_SET`	`CATEGORY_NOT_SET`	`0`
`TEAM_INVITER_CONTEXT`	`CATEGORY_TEAM_INVITER_CONTEXT`	`1`
`TEAM_POPULARITY`	`CATEGORY_TEAM_POPULARITY`	`2`
`TEAM_COLLABORATORS_JOIN`	`CATEGORY_TEAM_COLLABORATORS_JOIN`	`3`
`TEAM_COLLABORATORS_CREATE`	`CATEGORY_TEAM_COLLABORATORS_CREATE`	`4`
`PROJECT_INVITER_CONTEXT`	`CATEGORY_PROJECT_INVITER_CONTEXT`	`5`
`PROJECT_POPULARITY`	`CATEGORY_PROJECT_POPULARITY`	`6`
`ISSUE_DUE_SOON`	`CATEGORY_ISSUE_DUE_SOON`	`7`
`COMMENT_MENTION`	`CATEGORY_COMMENT_MENTION`	`8`
`COMMENT_REPLY`	`CATEGORY_COMMENT_REPLY`	`9`
`COMMENT_ASSIGNED`	`CATEGORY_COMMENT_ASSIGNED`	`10`
`ISSUE_APPROVAL`	`CATEGORY_ISSUE_APPROVAL`	`11`
`PR_REVIEW`	`CATEGORY_PR_REVIEW`	`12`