Hi,
We’re in the middle of the Forge adoption process, that is, converting our Jira Connect app to a Forge app, more precisely, a Connect-on-Forge app, which has no other Forge-specific modules, only the Connect module.
As the next step, we also want to make our app eligible for Atlassian Government Cloud, right after we get our app approved for Forge (and (re-)published on Marketplace).
We’ve already made most of the technical and administrative preparations (as I pointed out here), however, the entire workflow (the exact course of activities) needed to publish our AGC-compatible Connect-on-Forge app is not entirely clear to me, at least not based on the official documentation.
I’m interested if anyone has first-hand experience of the full procedure and could dispel my doubts, whether we shall publish a dedicated Forge (Connect-on-Forge) app for AGC, or is it sufficient to adopt the “backend” (ACSB or equivalent library) for our “soon-to-be” standard Connect-on-Forge app. It’s also more than enough, if anyone from the Atlassian staff could confirm or disprove my interpretation.
Please advise me!
Thanks in advance,
Márton