This page includes release notes and updates for Teamwork Graph app developers. Use this page to keep track of upcoming changes, deprecation notices, new features, and feature updates from Teamwork Graph.
For updates about changes to the Forge platform, see the Forge changelog in the Forge documentation.
Go to our developer community to ask questions. You may also be interested in the What's New blog for Atlassian Cloud where details of major changes are announced.
What's changing
The Teamwork Graph API can now be called directly from Forge app frontends (UI Kit and Custom UI) as part of the Teamwork Graph EAP. This is enabled via the new Forge bridge API, requestTeamworkGraph().
Previously, Teamwork Graph queries could only be executed from the Forge backend using @forge/api. This update allows you to fetch unified context across Atlassian products directly from the client side, reducing latency and simplifying app architecture.
What you need to do
Update the @forge/bridge package to the latest version in your app's frontend directory:
1
npm install @forge/bridge@latestEnsure your app has the required permissions in manifest.yml:
For Jira: read:graph:jira
For Confluence: read:graph:confluence
For more details on implementation and available data, see the requestTeamworkGraph documentation and the Teamwork Graph API guide.
To participate in this release, you must be enrolled in the Teamwork Graph EAP.
Forge connectors built on the @forge/teamwork-graph SDK can now use Orchestration - a platform-managed scheduling and execution layer that runs background ingestion work without an external scheduler or cron.
Instead of processing an entire data source in a single web request, you describe the work as a tree of tasks and hand them to Teamwork Graph. The platform then schedules your taskRunner function on a configurable recurring cadence (minutes, hours, or days), fans out work via child tasks, retries based on structured failure reasons.
Key capabilities:
graph.scheduleOrUpdateTask- Schedule a recurring root task per connection, or update an existing schedule in place.
graph.scheduleChildTask - Fan out from a running task into smaller per-item child tasks with persistent metadata.
graph.updateTaskStatus - Report success or failure with structured failureReason values (UNAUTHORIZED, RATE_LIMITED, AUTH_TOKEN_EXPIRED, etc.) so the platform can respond intelligently.
Long-running execution - Opt into a 15-minute execution budget via timeoutSeconds: 900 in manifest.yml.
For a step-by-step walkthrough with a Google Drive worked example, see https://developer.atlassian.com/platform/teamwork-graph/orchestration-for-forge-connectors/. For the underlying concepts (IDs, idempotency, lifecycle), see https://developer.atlassian.com/platform/teamwork-graph/orchestration-concepts/. For the SDK method reference, see https://developer.atlassian.com/platform/teamwork-graph/connector-reference/task-operations/overview/.
Rate this page: