[2-week notice] Connect EOS customer messaging to go live to production instances for apps that have declared a 'YES' migration intent

As per our previous announcement, we will be progressing admin-facing migration messaging for apps that have declared a migration intent of ‘yes’ on the Connected Apps page from the Developer Canary Program to production instances. This rollout will begin in approximately two weeks.

Apps affected in this rollout

• Apps that have declared connectToForgeMigration with a migration intent of "yes"

The following app categories have already been rolled out to receive admin-facing messaging as per our previous changelog:

• Apps that have declared connectToForgeMigration with a migration intent of "no"
• Apps that have declared connectToForgeMigration with a migration intent of "unsure"
• Apps that have not adopted the connectToForgeMigration module
• Apps without a Forge manifest (i.e., Connect apps)

What you need to do

1. Adopt the connectToForgeMigration module 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/).
2. Declare your migration intent as this determines which cohort your app falls into and when messaging appears.
3. Provide a migration URL. This URL will be surfaced directly in customer-facing notices, replacing the default Atlassian messaging with your app-specific guidance.
4. Preview the experience now using the Developer Canary Program. Customer messaging is already live on canary tenants for apps that have declared ‘yes’ to the migration intent. Install your app on a canary instance, navigate to the Connected Apps page, and confirm your migration URL renders as expected before the production rollout reaches your cohort.

More details

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. If an app utilises an affected feature but has not submitted a Connect EOS submission, it will not be exempted from this messaging.

For the full customer-facing experience (including more information on what admins will see), please visit the documentation here. This page will also be shortly updated to capture our rollout approach.