Forge Teamwork Graph API can now be called from app frontends
- Announced
- APIs
- forge-core-platform, teamwork-graph
- Scopes
read:graph:jiraread:graph:confluence- Severity
- notable, set by
reef/atlassian-rule-v1 - Source
- https://developer.atlassian.com/changelog/#CHANGE-3364
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/bridgepackage to the latest version in your app's frontend directory:
npm install @forge/bridge@latest
- Ensure 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.
The text above is Atlassian's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.