Rollout of Connect EOS admin messaging for apps with 'yes' migration intent
- Announced
- Tags
- forge-core-platform
- Severity
- info, set by
reef/atlassian-rule-v2 - Source
- https://developer.atlassian.com/changelog/#CHANGE-3434
As per our previous announcement, admin-facing Connect end-of-support (EOS) migration messaging on the Connected Apps page is now gradually rolling out to production instances for apps that have declared a migration intent of ‘yes’.
Apps affected in this rollout
- Apps that have declared
connectToForgeMigrationwith 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
connectToForgeMigrationwith a migration intent of "no" - Apps that have declared
connectToForgeMigrationwith a migration intent of "unsure" - Apps that have not adopted the
connectToForgeMigrationmodule - Apps without a Forge manifest (i.e., Connect apps)
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/). - Declare your migration intent as 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.
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.
The text above is the source's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.