Repository navigation
[changelog] [Announcement] Teamwork Graph API is now in Preview #47
Description
Activity
Status update (2026-10-07): treat this as EAP, not Preview, until it reappears.
CHANGE-3448 is no longer present in the Forge changelog RSS feed, the changelog page HTML, the aggregate Atlassian developer changelog, or the Teamwork Graph product changelog. The Teamwork Graph docs (API reference,
requestTeamworkGraph, Limitations and considerations) all still state EAP: no Marketplace or direct-link distribution, development environment only, org-admin install, API subject to change.The entry was in the feed when this issue was filed (guid fits the sequence between CHANGE-3447 and CHANGE-3453; pubDate 2026-10-05 11:17:20 GMT was copied from the item), so the likely explanation is that it was published and then retracted. The watcher did not archive the raw item at the time, so the original text cannot be re-verified. The watcher now stores raw
<item>XML for every filed entry and quotes Atlassian's description verbatim before any parity analysis.The guid has been removed from the watcher's seen-list so a re-publish will file a fresh issue. Parity work in this issue stays valid as a design target but should not be scheduled on the assumption that the API is Preview.
Changelog entry: CHANGE-3448
Published: Mon, 05 Oct 2026 11:17:20 GMT
Category: Announcement
Link: https://developer.atlassian.com/platform/forge/changelog/#CHANGE-3448
What is changing
The Teamwork Graph Consumption API is moving into Preview. It provides relationship-first querying across Atlassian Cloud objects and connected third-party tools via a unified GraphQL endpoint, covering Jira work items, Confluence content, Loom videos and meetings, external development artifacts, Goals, and Teams.
Until now this API was EAP-gated (test orgs only). Preview means apps can start calling it from the Forge runtime without a signup gate.
Parity impact for forge-sim
Simulator area: shims / product API (GraphQL).
@forge/apiGraphQL calls (requestGraph/ the gateway GraphQL route). Verify the@forge/apishim exposes whichever entry point Atlassian documents for the Teamwork Graph endpoint, and that the call is routed through the existing GraphQL mock layer (forge_mock_graphql) rather than falling through to an unmocked fetch.--proxy/ real-API mode: confirm the gateway endpoint is forwarded correctly with the PAT auth path.This is a new surface, not a change to existing documented behavior.