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

General Request for Comments (RFC)
, ,
15

Hello @EdmundMunday

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

  1. The Bitbucket REST API /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} 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
  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 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 CSP error
  5. (new) Do you have plans to implement module display conditions? We need them to hide the app from non-members of a workspace.
3 Likes