Recent changes to ease transition from Bitbucket Connect to Forge

[WendyG]

Hi,

Since our last post Bitbucket Connect to Forge migration tooling , we’ve received valuable feedback from vendors and have made the following changes to address them:

• Forge app menu items are grouped per app
• Forge product events have been enriched to include more fields
• workspaceId now always available in app.installation.contexts.workspaceId in Forge Invocation Token when using Forge Remote
• Connect application property api endpoints are accessible from its linked Forge app during migration phase. Note: app property api will be deprecated when Connect reaches EOL

Thanks

Wendy

[Renato]

Hi @WendyG,

Thanks for the update.

Regarding the deprecation of application properties, both Confluence and Jira retained their respective content and entity properties, which can be accessed and used via Forge. Why is Bitbucket taking a different approach?

Application properties are essential for extensions. In the Forge optimization guide, for instance, the recommendation is to use these properties instead of Forge storage to avoid the unnecessary costs.

Also, what is the plan for supporting display conditions in Forge if entity properties are not available? There is an open issue for this feature that is currently marked as a blocker.

Regards,
Renato

[joshp]

Hi @WendyG,

In addition to the above, could you please specify which Connect modules will not be ported to Forge by the Connect End-of-Support?

There is a page which specifies the Jira and Confluence modules for which Forge support is not planned:

Connect and Forge capabilities - not available

However I can’t find an equivalent for Bitbucket - I can just find this page which lists the currently-available equivalents:

Connect module equivalents

I’ve opened FRGE-2218 to ask that a Forge equivalent for fileEditors please be created because right now that is blocking our Forge migration, however I am unsure whether that will be done before Connect EoS.

Thanks, Josh

[WendyG]

Hi Renato, I have replied on the ticket you mentioned. Let’s discuss further there.

[WendyG]

Hi Josh,

Yes https://developer.atlassian.com/platform/forge/manifest-reference/modules/connect-module-equivalents/ shows the Bitbucket Connect modules + their Forge equivalents. We do not yet have a page that lists the official unavailable capabilities. I will followup and check if we can add one.

On fileEditors you are right it is not currently supported in Forge. Let’s discuss your use case further on the ticket you raised.

Thanks

Wendy