Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Issue with Forge remotes and "Runs on Atlassian" program

Daniel Platas
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 15, 2025

Hello,

I'm struggling to find a proper solution to become compatible with the "Runs on Atlassian" program while keeping my app capabilities, due to what appears to be inconsistencies in the Forge manifest behaviour.

I have this Rovo agent that fetches public documentation from my company's instance to help guide users -- this doesn't involve customer data, so it should still be compliant with the RoA program baselines. To add permissions to this operation, I set up this "remote" attribute in my `manifest.yml` file, according to this documentation:

permissions:
external:
fetch:
backend:
...
- remote: "remote-docs"
remotes:
- key: remote-docs
baseUrl: "https://docs.adaptavist.com"
operations:
- fetch

This is looking all good; however, it doesn't work. This is a message running `forge eligibility -e development` after deploying:

ℹ The version of your app [8.0.0] that's deployed to [DEV development] is not eligible for the Runs on Atlassian program.
- App is using remote services
- App is egressing data

Is this a bug in the manifest configuration? Am I missing something?

On the other hand, I've successfully managed to make this work by using the config:

permissions:
external:
fetch:
backend:
...
- address: "docs.adaptavist.com"
category: "analytics"
inScopeEUD: false

Although I can guess this is not very orthodox, can I use this as a workaround if the previous, official way is suffering from a bug or is not expected to work at all for some reason?

Thanks in advance.

1 answer

0 votes
Sunny Ape
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 15, 2025

Howdy @Daniel Platas 

Because your Forge app is egressing data outside of Atlassian's domain, it's not strictly compliant with the eligibility requirements for Runs on Atlassian.

This is a contentious topic, and you'll find quite a few threads like this one over on the Developer's Community forum, where all matters regarding Forge and the Runs on Atlassian program are discussed, and where I suggest you add your voice :)

Suggest an answer

Log in or Sign up to answer