Issue Summary

Vendors migrating from Jira Cloud Connect to Forge Remote cannot reliably preserve legacy app URLs on the Jira domain. Old Connect URLs under plugins/servlet/ac/<app-key>/... become dead after migration and there is no supported way for vendors to redirect these to the new Forge URL pattern /jira/apps/{APP_ID}/{ENV_ID} at the host (Jira) page level. This breaks bookmarks, documentation links, forum posts, emails, and 3rd‑party integrations that rely on the old URLs.

Steps to Reproduce

Steps to Reproduce

1. Install a Jira Cloud Connect app that exposes a general page at a URL like:
   https://<site>.atlassian.net/plugins/servlet/ac/jira-timesheet-plugin/...

1. Migrate the app UI to a Forge Remote app reachable via:
   https://<site>.atlassian.net/jira/apps/{APP_ID}/{ENV_ID}[...]

1. Update / remove the Connect functionality so the Forge app is the primary experience.

1. From a bookmark, doc link, or external system, open the old Connect URL
   plugins/servlet/ac/jira-timesheet-plugin/....

Expected Results

• A supported, durable mechanism or pattern to:

• • Redirect legacy Connect URLs under plugins/servlet/ac/<app-key>/... to the new Forge /jira/apps/{APP_ID}/{ENV_ID} URLs at the host page level, not just inside the iframe.

• • Handle mixed Connect/Forge rollout per tenant (during phased migrations) so that a single legacy URL can:

• • • Route to Connect if the tenant is still on Connect, or

• • • Route to Forge if the tenant has migrated.

Actual Results

• Once the Connect module is removed, plugins/servlet/ac/<app-key>/... no longer resolves at all; vendors have no hook to intercept or redirect those Jira-domain URLs.

• While a Connect module still exists:

• • HTTP 30x from the vendor backend only affect the iframe, not the top-level Jira URL, and cannot reliably open /jira/apps/{APP_ID}/{ENV_ID}{}.

• • Only AP.navigator.go from within the Connect iframe successfully changes the top-level Jira location to /jira/apps/{APP_ID}/{ENV_ID}{}.

• There is no documented platform-level redirect or official guidance on how vendors should handle long-lived external references (bookmarks, docs, forum posts, emails, 3rd-party integrations) that target the old plugins/servlet/ac/... URLs after migrating to Forge Remote.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available