This all feels like a good stab in the back.
Our concerns have been highlighted very well by others above. Two things I’d like to add:
- Forge currently does not natively support collecting traces (something I inquired about more than a year ago). Functions run like a black-box, making us hesitant to run any code on Forge with production workloads.
- Our Connect app uses OAuth2 to connect to an external system,
asAppwhich is not available on Forge. I have talked to Atlassian about this gap since Sep 2021, when providers were launched (close to 4 years ago), and came up with workarounds that I am not comfortable shipping to production (mostly with security implications for Forge users).
To @ChrisHemphill1 and the Atlassian decision-makers who came up with this plan: I’d like to understand what led you to the conclusion that partners on Connect should be financially punished for not moving to Forge by January 2026.
To be clear on our position: We have been trying to migrate from Connect to a Forge native app for many years (3+), we are on board with this, but every now and then it feels some people at Atlassian are on a different boat.