connectToForgeMigration / willMigrateToForgeBeforeEOS: YES ––– no visible change before cohort rollout date?

Forge
, ,
1

Hi everyone!

We in a team are migrating app from Connect to Forge. We already migrated part of the Connect modules. And recently we see that ‘Legacy’ tag next to our app. According to docs we can modify inner app banner to blue: Connect to Forge migration
So we’ve added the connectToForgeMigration module to our Forge manifest with:

connectToForgeMigration:

  • key: appname-migration-declaration
    migrationGuideUrl: our-migration-guide-url
    willMigrateToForgeBeforeEOS: YES

Locally it works, and even the ‘Legacy’ tag disappear, but after we also deployed that change to our staging environment and installed on a test site and in “Connected Apps” page it still shows the generic default messaging - no blue banner, no link to our guide.

I also found this page that kinda says that this connectToForgeMigration addition will not work until mid August (if I understood correctly): What admins see on the Connected Apps page

Wanted to confirm a couple of things:

  1. Is it expected that a correctly-declared YES app shows no visible change at all until Atlassian’s own rollout reaches the YES cohort and so there’s nothing more we can do on our end to make the blue banner/link appear sooner, regardless of when we deploy the manifest?
  2. Is there any way to preview/test the YES-cohort banner behavior ahead of the general rollout (e.g., a feature flag, an allowlisted test site, a dev-mode override), so we can validate our declaration is correct before mid-August?
  3. Separately: does this module have any effect on the LEGACY badge shown next to an app’s name in the Manage apps list, or is that badge governed purely by “app still ships a Connect module” regardless of migration intent declared?

Thanks!

2

Just quickly responding to your questions:

  1. Before the rollout started, if you had enrolled into the developer program for your Jira or Confluence instance, then you would have been able to see what happened when you answered yes. However, now all instances are following the exact same rollout pattern and you will not be able to see it until August.
  2. No unfortunately at this point in time there is not, but you can look at our documentation to see what the message will look like.
  3. Putting in your migration intent will not remove the legacy badge. It will simply improve the experience for customers by giving them confidence that you will or will not be off Atlassian Connect before the platform becomes unsupported.

I hope this helps and thank you for the good questions.

3

thanks a lot for the reply! helps a lot to understand the flow