Create Permissions

[jonathan.revah]

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.

[Daniil Penkin]

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

[jonathan.revah]

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.

[Daniil Penkin]

Hello @jonathan.revah,

Thanks for reaching out.

Can you elaborate on the flow you're following to create a repository? Is it via UI? If so, is my understanding correct that even though you select your Org's team in the dropdown (see screenshot), the new repository ends up in your own account?

Cheers,
Daniil