The Teamwork Graph API is available through Forge's Early Access Program (EAP).
EAPs are offered to selected users for testing and feedback purposes. These features are unsupported and are subject to change without notice.
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.
The AtlassianUserViewedDocuments relationship is a logical relationship that provides a unified view of documents a particular user viewed across different tools.
Relationship type: Logical
TTL (Time To Live): 30 days
| From object types | To object types |
|---|---|
Atlassian user - ati:cloud:identity:user | Confluence blogpost - ati:cloud:confluence:blogpost |
Confluence page - ati:cloud:confluence:page | |
External branch - ati:cloud:jira:branch, ati:cloud:graph:branch | |
External build - ati:cloud:jira:build, ati:cloud:graph:build | |
External commit - ati:cloud:jira:commit, ati:cloud:graph:commit | |
External conversation - ati:cloud:graph:conversation | |
External deployment - ati:cloud:jira:deployment, ati:cloud:graph:deployment | |
External document - ati:cloud:jira:document, ati:cloud:graph:document | |
External message - ati:cloud:graph:message | |
External repository - ati:cloud:jira:repository, ati:cloud:graph:repository | |
External vulnerability - ati:cloud:jira:vulnerability, ati:cloud:graph:vulnerability |
This relationship encompasses the following relationship types:
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 2query AtlassianUserViewedDocuments_CypherQuery($cypherQuery: String!, $params: CypherRequestParams) { cypherQuery(query: $cypherQuery, params: $params) { edges { node { columns { value { ... on CypherQueryResultNode { id data { __typename ... on ConfluenceBlogpost { id } ... on ConfluencePage { id } } } } } } } } }
1 2{ "cypherQuery": "MATCH (user:AtlassianUser {ari: $id})-[:atlassian_user_viewed_documents]->(blogpost:ConfluenceBlogpost) RETURN blogpost", "params": { "id": "$id" } }
Rate this page: