Forge Teamwork Graph Preview: Issue-to-PR discovery and data egress for an external SaaS

Igor Diniz Maciel

Hello Atlassian Developer Support,

We are evaluating a read-only integration between our external multi-tenant SaaS, Engineering System Model (ESM), and development relationships already indexed by Jira through the standard GitHub for Jira integration.

The Teamwork Graph Consumption API entered Preview on October 15, 2026. We found the documented curated query:

jiraWorkItemLinkedExternalPullRequests(id: ID!)

This query appears to solve our requirement: retrieving pull requests already associated with Jira work items, without relying on textual matching of issue keys in PR titles or descriptions.

We have already verified a real use case.

Our Atlassian connected graph returns an authentic Jira Work Item → GitHub Pull Request relationship, even when the Jira issue key does not appear in the PR title or description.

Before creating or installing a Forge application, we would appreciate clarification on the following points.

1. Curated query availability

Is jiraWorkItemLinkedExternalPullRequests supported in the current Teamwork Graph Forge Preview for Jira work items linked to pull requests through the standard GitHub for Jira integration?

Should it return the same relationships already visible in Jira Development and Atlassian's connected graph, subject to user permissions?

2. Required permissions

Are the following Forge scopes sufficient?

• read:graph:issue:jira
• read:graph:pull-request:external

Are additional permissions or organization-level configurations required?

How should we distinguish between no relationship existing and an empty response caused by missing permissions?

3. Data egress to an external SaaS — our main question

The Teamwork Graph limitations documentation describes restrictions on transferring Graph data outside Atlassian.

Would an authorized external SaaS be permitted to receive and persist only the minimum correlation metadata returned by a read-only Forge application?

For example:

• Jira work item ID or ARI
• GitHub pull request ID and URL
• Relationship provenance
• Relevant relationship timestamps, when available

Our SaaS would use this information to verify and enrich the pull request through its own authorized GitHub App installation.

If this data transfer is restricted, what supported architecture would Atlassian recommend for this integration?

4. Authentication and integration architecture

Can the Teamwork Graph API be called directly by an e

Arkadiusz Wroblewski

Hello @Igor Diniz Maciel

I see the bigger concern is data egress, as Atlassian documents restrictions on exporting Teamwork Graph data.

https://developer.atlassian.com/platform/teamwork-graph/limitations-and-considerations/

I recommend confirming your external SaaS use case with the Teamwork Graph team in the Developer Community before you implement it. Everything is too fresh now to answer that deterministically in the Community.

Best,

Arek🤠🧙‍♂️