You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hey guys,
So recently our organization tightened up permissions and stopped allowing all users to create new repositories. The issue is, if you attempt to create one without the correct permissions, it just produces the repository under your namespace.
Really, it should return an error of some kind so we know what's going on.
Just thought you guys would want to know.
Hi Daniil,
The flow not quite like that. If I go into one of my organization's projects and hit 'create repo', it'll take me to a page that looks like this:
https://bitbucket.org/repo/create?owner=organization_name
The owner will be listed as me, but it won't display any error when going to that page and will obviously create a repo under my name.
Ok, now I get what you mean. Thanks for the details!
So yes, you're right, in this case we silently ignore the context you came from and preselect some other account you can create repositories in – in your case it is your personal account (but might be some other team, for instance).
I agree we should show some hint that the context has changed. I mean that there's no bug in the behaviour you observed, it's rather a silent fallback to another account which is easy to miss. I'll check with the team on what we can do there. Do you mind creating a ticket with the same description in our public issue tracker? This way you'll be notified as soon as we do something about this issue.
Cheers,
Daniil