Thanks for your feedback on this. We do acknowledge that there are cases where migration may be blocked by current platform limitations. As an aside, we’re actively working to be more transparent with partners about where we are drawing the line for Connect to Forge work before end of support, so you have a clearer view as well.
In particular, we’ve kicked off the Connect EOS triage process described here: https://community.developer.atlassian.com/t/tell-us-what-you-need-before-connect-eos-submit-your-critical-migration-blockers/99433
This process is in flight now, and is designed to:
-
identify the remaining critical migration blockers that we’ll consider before Connect end of support
-
make explicit, auditable decisions about what you can expect to be delivered by December 2026
-
give partners a stable picture of the final scope, so you can factor it into how you plan migrations and how you communicate timelines and constraints to customers
When we go live with this messaging, we expect the above information to give partners additional clarity to draw on when communicating with customers. We are currently exploring the option of having structured statuses to surface in the messaging itself as there seems to be an appetite for it.