Teamwork Graph API is now in Preview

The Teamwork Graph Consumption API is now moving into Preview, providing relationship-first querying across Atlassian Cloud objects and connected third-party tools.

What's changing

The Teamwork Graph API lets you query connected context across Jira work items, Confluence content, Loom videos and meetings, external development artifacts, Goals, and Teams using a unified GraphQL endpoint.

###

More details

Key capabilities in this release include

• Curated queries: Supported, typed GraphQL fields for common traversals (such as atlassianUserAssignedJiraWorkItems or confluencePageContributors) with built-in Relay cursor pagination (first, after). No query registration is required.
• Persisted Cypher queries: Custom graph traversals registered ahead of time to receive a persistent query key (queryKey), which you execute at runtime via the customQuery GraphQL root field.
• Granular object-level scopes: Permissions now use fine-grained scopes following the read:graph:<object>:<product> pattern (such as read:graph:issue:jira and read:graph:page:confluence), giving site administrators precise control in Connected Apps.

What you need to do

• Update your Forge app manifest.yml permissions to request the specific read:graph:<object>:<product> scopes required for your queries.
  • If your app currently uses ad-hoc runtime Cypher queries, migrate to typed fields in the curated queries documentation or register custom queries using the persisted Cypher queries guide.