-
Bug
-
Resolution: Fixed
-
High
-
5.11.1, 5.12.5, 5.13.2, 5.14.5, 5.15.7, 6.0.5, 6.1.6, 6.2.8, 6.2.9, 6.4.2, 6.5.1, 6.3.4, 6.6.3, 6.8.0, 6.7.3, 6.8.1
-
None
-
9
-
Severity 2 - Major
-
16
-
Update (16/04/2020)
Please follow BAM-20900 for additional information
Problem
Because of Bitbucket cloud rest api change https://developer.atlassian.com/cloud/bitbucket/bitbucket-api-changes-gdpr/
I cannot
- create and update via UI
- upload via specs
Bitbucket cloud private and public repositories if user is an owner, for teams it works.
The UI displays the following errors when performing "Test Connection":
- Invalid Username
- We couldn't connect to the repository. The details you provided were invalid.
Note: This affects all versions before 6.9.1, 6.8.3
Workaround:
Define repository as a Git or Mercurial repository
Limitations of workaround:
- Build status integration with Bitbucket Cloud isn't supported by the Git type repository
- Create plan branch when pull request is created (automatic pull request detection) isn't supported.
- Lack of easy-to-use drop downs for branch and repository selection when configuring a repository.
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
Cannot save Bitbucket Cloud Repository: Invalid Username and We couldn't connect to the repository errors
-
-
Resolution: Fixed
-
High
-
5.11.1, 5.12.5, 5.13.2, 5.14.5, 5.15.7, 6.0.5, 6.1.6, 6.2.8, 6.2.9, 6.4.2, 6.5.1, 6.3.4, 6.6.3, 6.8.0, 6.7.3, 6.8.1
-
None
-
9
-
Severity 2 - Major
-
16
-
Update (16/04/2020)
Please follow BAM-20900 for additional information
Problem
Because of Bitbucket cloud rest api change https://developer.atlassian.com/cloud/bitbucket/bitbucket-api-changes-gdpr/
I cannot
- create and update via UI
- upload via specs
Bitbucket cloud private and public repositories if user is an owner, for teams it works.
The UI displays the following errors when performing "Test Connection":
- Invalid Username
- We couldn't connect to the repository. The details you provided were invalid.
Note: This affects all versions before 6.9.1, 6.8.3
Workaround:
Define repository as a Git or Mercurial repository
Limitations of workaround:
- Build status integration with Bitbucket Cloud isn't supported by the Git type repository
- Create plan branch when pull request is created (automatic pull request detection) isn't supported.
- Lack of easy-to-use drop downs for branch and repository selection when configuring a repository.
-
Marcin Walerianczyk
-
- Votes:
-
2 Vote for this issue
- Watchers:
-
28 Start watching this issue
- Created:
- Updated:
- Resolved: