Production rollout starting - Connect EOS customer messaging for admins
- Announced
- APIs
- adopting-forge-from-connect, forge-core-platform
- Severity
- info, set by
reef/atlassian-rule-v1 - Source
- https://developer.atlassian.com/changelog/#CHANGE-3366
As per our previous announcement, admin-facing Connect end-of-support (EOS) migration messaging on the Connected Apps page is now rolling out to production instances. This messaging, which was previously limited to Developer Canary tenants, is being deployed in staggered cohorts.
The following app categories will begin receiving admin-facing messaging in production:
- Apps that have declared
connectToForgeMigrationwith a migration intent of NO - Apps that have declared
connectToForgeMigrationwith a migration intent of UNDECIDED - Apps that have not adopted the
connectToForgeMigrationmodule - Apps without a Forge manifest (Connect apps)
Apps that have declared connectToForgeMigration with an intent of YES are estimated to begin receiving admin messaging in mid-August. We will provide another changelog entry at least 2 weeks before that change proceeds.
What you need to do
- Adopt the
connectToForgeMigrationmodule in your Forge manifest for each major version of your app (https://developer.atlassian.com/platform/adopting-forge-from-connect/connect-to-forge-migration-module/) if you have not already. - Declare your migration intent - this determines which cohort your app falls into and when messaging appears.
- Provide a migration URL - this URL will be surfaced directly in customer-facing notices, replacing the default Atlassian messaging with your app-specific guidance.
For details about the full customer-facing experience, see What admins see on the Connected Apps page.
Exemptions
Apps that are blocked by an accepted Connect EOS FRGE ticket will be exempt from customer messaging until one month past the delivery date of the blocking feature. This exemption list is determined exclusively by partners who have submitted a Connect EOS Submission request on these accepted tickets, providing a valid use case and explanation and applies to only the apps that have been marked as affected by the feature in the submission. If an app utilises an affected feature but has not submitted a Connect EOS submission, it will not be exempted from this messaging.
More details: [object Object]
The text above is Atlassian's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.