I’m planning a new Forge app and want to design for Runs on Atlassian eligibility
from line one rather than retrofit it later.
The documented criteria are: no data egress (except analytics carrying no in-scope
end-user data), exclusively Atlassian-hosted compute and storage, and data
residency matching the host product.
What I can’t determine from the docs is how inbound and user-initiated data
flows are treated. Could someone confirm whether these preserve eligibility?
-
Inbound push from external CI. A customer’s CI pipeline (Jenkins, GitHub
Actions) POSTs results to a Forge web trigger in my app. My app never calls out
to the CI system — data flows only inward. Eligible? -
Customer-initiated file import. A customer uploads a file through my app’s
UI; the app parses it and writes to Forge storage. No outbound network call.
Eligible? -
Customer-initiated export. My app generates a PDF/CSV from Forge storage
and the customer downloads it in the browser. Eligible?
And two structural questions:
-
Is eligibility evaluated per app? Could I ship an eligible core app plus a
separate, non-eligible integration app under the same partner account? -
Is eligibility re-evaluated automatically on each new app version, or assessed
once?
The reason this matters: if inbound-only flows are fine, a whole class of app can
be built ROA-native that I’d otherwise assume was disqualified.