# RFC-86 Bitbucket Connect to Forge: Input on the Migration Process

**URL:** <https://community.developer.atlassian.com/t/rfc-86-bitbucket-connect-to-forge-input-on-the-migration-process/89322>\
**Category:** Request for Comments (RFC)\
**Tags:** bitbucket, atlassian-connect, forge\
**Created:** [February 21, 2025, 12:04am UTC](https://community.developer.atlassian.com/t/rfc-86-bitbucket-connect-to-forge-input-on-the-migration-process/89322 "2025-02-21T00:04:07Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![aokulovich](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/aokulovich/32/37888_2.png) [@aokulovich](https://community.developer.atlassian.com/u/aokulovich)\
**Post date:** [October 22, 2025, 8:41am UTC](https://community.developer.atlassian.com/t/rfc-86-bitbucket-connect-to-forge-input-on-the-migration-process/89322/15 "2025-10-22T08:41:58Z")

</div>

Hello @EdmundMunday

Here are some questions/issues we would like to clarify:

1. The Bitbucket REST API [/users](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-users/#api-group-users) group endpoints surprisingly aren’t available in Forge. Although the documentation doesn’t allow it, we can still make requests to the [/users/{selected\_user}](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-users/#api-users-selected-user-get) endpoint to retrieve the user information. However, the avatar link always leads to a default one for all users. The lack of a correct avatar link makes the UX worse, as we widely use those avatars in the app UI. Can this be fixed? [BCLOUD-23823](https://jira.atlassian.com/browse/BCLOUD-23823)
2. Are there any updates on the user migration process and linking the Forge app with the existing Connect app?
3. ~~Lack of the `Global page` module reduces our app functionality by half and is a huge blocker for us to move to Forge. Can you share an approximate timeline when it becomes available?~~ UPD. [exists](https://developer.atlassian.com/platform/forge/manifest-reference/modules/bitbucket-workspace-global-page/) now
4. Bitbucket integration functionality in Forge libraries:
  1. `“@forge/bridge”: “5.5.0”`. `router.navigate` doesn’t support navigating to other pages of the app. This is forcing us to create a URL using a tricky logic that parses parts of the current page URL and makes a new one from them.
  2. `"@forge/api": "6.1.4"`. `authorize` doesn’t allow checking user permissions for Bitbucket entities in Forge Functions.
  3. `“@forge/bridge”: “5.10.2”`. `requestRemote` execution [causes](https://community.developer.atlassian.com/t/requestremote-bridge-api-is-now-available-for-integrating-remotes-directly-from-the-ui-client/97422/16) CSP error

5. (new) Do you have plans to implement module [display conditions](https://developer.atlassian.com/platform/forge/manifest-reference/display-conditions/)? We need them to hide the app from non-members of a workspace.

---

_[View the full topic](https://community.developer.atlassian.com/t/rfc-86-bitbucket-connect-to-forge-input-on-the-migration-process/89322)._