Issue Summary

After migrating our app from Connect on Forge to Forge Remote, diagrams created previously (while running the Connect-on-Forge version) still appear in search results, but opening those results navigates to the old Connect content view URL/module instead of the Forge custom content view module configured for the same custom content type.

We expected Atlassian’s custom content migration behavior to update the target endpoint/module automatically, because:

• we migrated all Connect modules to Forge modules for Forge Remote, and

• our custom content configuration includes migratedFromConnect.

However, the link generated from Atlassian Search continues to point to the legacy Connect route.

Steps to Reproduce

1. Create a Gliffy Diagram/Custom content App Connect on Forge
2. Clicking the search result opens the diagram via the legacy Connect content view instead of the Forge custom content view.

   Custom content configuration in Forge Remoteconfluence:customContent:
     - key: gliffy-diagram
       title: Gliffy Diagram
       description: A custom content type for storing and displaying Gliffy diagrams
       icon: resource:gliffy-viewer-resource;gliffy-logo.svg
       bodyType: raw
       supportedContainerTypes:
         - page
         - blogpost
         - space
       supportedChildTypes:
         - attachment
         - comment
       # Note: supportedSpacePermissions is intentionally omitted to remove
       # this custom content from the Apps page dropdown while maintaining
       # functionality. Atlassian will determine permissions at runtime
       # rather than using explicit “create”, “read”, “delete” permissions.
       indexing: true
       preventDuplicateTitle: false
       migratedFromConnect: true
       resource: custom-content-resource 

Expected Results

For custom content types marked with migratedFromConnect, search result links should open the content using the Forge module (Forge custom content view) after migration to Forge Remote.

Expected URL:
 
 https://<site>>/wiki/display/FR/customcontent/<custom-content-id>

Actual Results

The search result opens using the legacy Connect module/URL (Connect content view) instead of the Forge module configured for the custom content.

Actual URL:
 
 https://<site>/wiki/plugins/servlet/ac/com.gliffy.integration.confluence/gliffy-confluence-fullscreen-viewer-launcher?content.plugin=ac%3Acom.gliffy.integration.confluence%3Agliffy-diagram&space.key=COF&content.id=4915217&content.version=1&space.id=6094850&content.type=custom&search_id=be391478-afa5-4edd-9db5-83e91d23362e

Workaround

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