[Bug][Bitbucket] Add Data Scope fails with CHANGE-2770 after successful Bitbucket Cloud connection

[pegedece]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

When creating a Bitbucket Cloud connection in Apache DevLake v1.0.3-beta13, the connection test succeeds, but the onboarding workflow fails during the "Add Data Scope" step when DevLake attempts to retrieve Bitbucket workspaces/repositories.

The UI displays the following backend error:

CHANGE-2770 - Functionality has been deprecated
HTTP 410 Gone

The stack trace points to:

plugins/bitbucket/api.listBitbucketWorkspaces
plugins/bitbucket/api.listBitbucketRemoteScopes

As a result, no repositories can be selected and the onboarding process cannot be completed.

Environment(s) tested

The issue was reproduced in multiple independent environments:

1. Upgraded installation

   • Apache DevLake v1.0.3-beta13
   • Upgraded from v1.0.3-beta12
   • Podman on RHEL 9
   • MySQL 8
   • Bitbucket Cloud

2. Fresh installation

   • Apache DevLake v1.0.3-beta13
   • Podman on RHEL 9
   • New database
   • Bitbucket Cloud

3. Fresh installation

   • Apache DevLake v1.0.3-beta13
   • Ubuntu on WSL
   • Podman
   • New database
   • Bitbucket Cloud

The same behavior was observed in all three environments.

What do you expect to happen

Expected behavior

DevLake should list the available Bitbucket workspaces and repositories so that a Data Scope can be selected.

Actual behavior

DevLake fails when requesting the available Bitbucket workspaces and returns:

CHANGE-2770 - Functionality has been deprecated

HTTP 410 Gone

The stack trace references:

plugins/bitbucket/api.listBitbucketWorkspaces

and

plugins/bitbucket/api.listBitbucketRemoteScopes

preventing repository selection and completion of the onboarding workflow.

Notes

Creating a connection through the Config UI is currently affected by a separate issue. Clicking "Create New" triggers a React error (#31), preventing connection creation from the web interface.

As a workaround, the Bitbucket connection used for testing was created successfully through the REST API.

This React issue appears to be independent from the Bitbucket workspace/repository discovery issue described in this report.

How to reproduce

1. Deploy Apache DevLake v1.0.3-beta13 using the official containers.

2. Create a Bitbucket Cloud connection using a valid Atlassian API Token.

3. Verify that the connection test succeeds.

4. Create a new project (or start the onboarding workflow).

5. Select the Bitbucket Cloud connection.

6. Continue to the "Add Data Scope" step.

7. Wait for DevLake to load the available Bitbucket workspaces/repositories.

8. Observe that DevLake fails and displays an error containing:

   CHANGE-2770 - Functionality has been deprecated
   HTTP 410 Gone

9. Review the backend stack trace, which references:

   plugins/bitbucket/api.listBitbucketWorkspaces
   plugins/bitbucket/api.listBitbucketRemoteScopes

Expected result:
DevLake should list available Bitbucket workspaces and repositories so that a Data Scope can be selected.

Actual result:
DevLake fails to retrieve Bitbucket workspaces and returns HTTP 410 with Atlassian CHANGE-2770.

Anything else

Additional findings

• The issue is reproducible on both upgraded and fresh installations.
• The issue is reproducible on different operating environments (RHEL 9 and Ubuntu/WSL).
• API Token authentication appears to work correctly.
• Connection testing succeeds.
• The failure occurs only when DevLake attempts to retrieve Bitbucket workspaces/repositories for Data Scope selection.
• The backend response references Atlassian change CHANGE-2770 and returns HTTP 410 Gone.

Version

v1.0.3-beta13

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct