@ChrisHemphill1 we keep telling Atlassian that Forge isn’t ready yet for a big Connect migration (see here and here) and it looks like our fears are coming true.
We also have hard blockers for migrating only our top 3 apps (1, 2, 3, 4). Also, major parts within Forge are unstable with EAP and Preview notices everywhere. We discover new Forge bugs and inconsistencies with Connect every week (example 1 and 2 just for Jira post-functions) and there are important parts that don’t seem to scale for large apps. We can’t even see production logs and would get charged for > 300 GB of system logs without being able to influence those system logs.
We’ll probably have to drop some features for our apps in order to convert them to Forge by the end of 2025. The alternative of getting 4% (and later 8%) less revenue share is too uncertain, since we won’t have any guarantee when those missing Forge features will be delivered by Atlassian.
Please reconsider your timeline and allow your own teams more time to make Forge a platform that developers want to migrate to and aren’t being pushed on with so many hard compromises.