Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


How to add repository owned by a team?


I wanted to add repository owned by a team to linked repositories but during save the credentials are not accepted with message "Invalid username". In the background bamboo is making a call to a following API endpoint:

404 -

If I put a name of a team as "Username" than a  "linked repository" can be saved but any further requests (e.g. pulling changes from repository) are ending in 401 "Unauthorized" errors.

What is a correct solution to this problem?


I am using Bamboo version 6.8.1 and Bitbucket Cloud.

1 answer

1 accepted

2 votes
Answer accepted
Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 18, 2019 • edited

Hi @kapusj01

Yes, this problem is recent and caused by the GDPR required changes in the API. We are really sorry that this is causing you trouble. You can find more details about this event and how to overcome it here:

Basically, you have two options at the moment:

  • Upgrade Bamboo to 6.9.1
  • Use the Git or Mercurial repository types to connect with Bitbucket

Please let me know if you need any help to move forward or any clarification.

Thank you for bringing this up.

Thank you for the answer. After upgrade to 6.9.1 everything works fine again

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events