Hey Nick,
Thanks for your feedback. We hear the concern around creating a consistent experience for admins.
Our current thinking is to explore adding the structured status options directly into the in‑product messaging (e.g. “migrating by X”, “no action needed”, “contact partner”), so that admins get a consistent experience without needing to leave the surface. For this to work reliably and at scale, our current exploration reveals the most viable path is making this available through the manifest, which would give us a standardised way to collect and display that information consistently across all apps.
We envision the URL that partners provide to be additive information for the customer. In scenarios where partners already have their own way of notifying their customer base about planned migrations, this solution allows them to reuse their existing structure. For others who may not have the same methods of notification, we won’t necessarily restrict the type of URL provided to us, in theory, this URL could be hosted on platforms like Google, GitHub, or even another Confluence page.
I recognise this doesn’t solve for pure Connect apps out of the box. As noted in the earlier thread, for those apps our proposal is to surface actions that either encourage customers to upgrade to the latest version (where it runs on Forge) or direct them to contact the partner. We’re open to feedback on whether that gap is acceptable or needs a different approach.
Regarding your last point on missing capabilities, I’ve mentioned above that we’ve kicked of the following process: https://community.developer.atlassian.com/t/tell-us-what-you-need-before-connect-eos-submit-your-critical-migration-blockers/99433. Please engage in this as we want to give partners explicit decisions on what will be delivered before December 2026. Our aim is that this gives you enough clarity to form realistic timelines and expectations rather than generating more questions.