how can i view the emails address of bitbucket account holders

[Saravanan S]

We have many groups on our organization in that groups that will show only user names. i want view the email id's of that user for removal of user relieving time. 

[AlexV]

Yes, I am surprised by the answer. I have 20-30 mistery users and I can't get their email address via admin ui/portal/or API?

[nekcih]

I was able to get the emails by going to https://bitbucket.org/{username}/workspace/settings/user-directory and clicking the export button. This downloads a csv with the email addresses.

[Angelo Evangelista]

Still no good solutions for this, lol. But I've found a dirty workaround to this. Simply use the internal bitbucket site api, since it shares the same bearer token auth method:

https://bitbucket.org/api/internal/workspaces/<YOUR_WORKSPACE>/groups/<GROUP_SLUG>/members

It's a paginated response, so You'll have to handle that. You can also add a query param "fields" to fetch only specifics fields, such as our precious email there

The member will be in the format below:

This is not the best, You know. But we work with what We have :p

[Oliver McPheely]

Thank you for this, it's ridiculous that this actually works and it feels more like a bug than a feature but it does at least solve the problem.

[Ryan Hilliker]

It seems Atlassian's interpretation of GDPR is that users of their services are able to maintain complete anonymity via any services that may interact with their API's; whether that's BitBucket, JIRA, or Admin API endpoints. Their position seems to be that names and email addresses are off-limits.

What is interesting is that they still have documented API's all over the place that claim to return user information, such as from here and that would require an Admin API  key that expires, but it'll return an empty array. So Atlassian has chosen to give its customers the advice that they should export a list of all of their user data, instead of using secure API's, because then it's your problem and not theirs. A pretty bizarre scenario.

I have discovered a bit of a bug on their end that will expose email addresses on occasion for specific staff who create and review PR's. You have to use this API and iterate over author.raw to get email addresses from this endpoint: https://api.bitbucket.org/2.0/repositories/{workspace}/{repo}/refs/branches (see documentation here)

[AlexV]

Oh oh @Ryan Hilliker  - you're about to get permabanned. ;p

[Cristhian Benitez]

This talks about how the security is manage inside the company

[Dirk van Rensburg]

I had this same issue because the 'User directory' now also contains the "Users on plan" I could previously figure out who's who by going to the latter.

The only way I have found to figure this out now is to add the users to a group and then going to the "User groups" view and looking up the group. Emails are shown there along with the user's name.

[Andy Royle]

Adding my voice to the above. This is a ridiculous configuration. Carrying out an audit where we have developers from different suppliers and knowing who is with which so we can terminate access when we end a relationship is essential. This cannot be done with username alone !

[Ana Retamal]

Hi Saravanan,

You won't be able to see the email address of the users. You can only see their name and username. This can be found on the link https://bitbucket.org/account/user/<username>/plan-users/ (make sure to replace <username> with your actual username).

Hope that helps!

Ana

[Saravanan S]

Thanks for the reply.  when user getting relieving we need to remove them accordingly. some time same name will be there we cannot identify with the user name. 

[Marek Uhel]

This is crazy - being part of admin group in Jira&Confluence, you can really manage users, you can see the username and email. Jumping into bitbucket, you have to guess which email is behind the user, as you'll see only the same name and duplicated entries.

Such usability, as removing all the user's entries and and adding the "valid" email back, seeing in paid, "professional" product for the first time.

[Sam Mugel]

Agreed. What is the reason for this choice?

[AlexV]

Perhaps someone who never managed a system decided it was a good idea.

It's obviously not, but someone thought it was.

[Erez Mor]

Poor decision. As an admin I need a way to track the user email, this is the only unique value. The user can set a nickname for whatever he likes.

[Tonia Hatter]

I have the same exact issue. I now have a user with two different accounts between jira and bitbucket and I didn't know that because I can't see their bitbucket email profile. Poor configuration Atlassian.

[AlexV]

I bet you another $5 that this isn't poor configuration. This is poor understanding of what compliance means.

[Jason Holladay]

This is unacceptable.  When will it be fixed?

[Panos Laganakos]

Please fix this. I spent 20' to figure out which person is which. This is insane.

[nbourdon]

Please fix this. It's absurd. Does nobody from Atlassian actually use Atlassian tools?

Edit: after looking around some more, not all users on our account even have their usernames displayed! How does Atlassian decide if they're going to show the username for a certain user or not? How am I even supposed to use the "solution" above if I don't know what a user's username is? Why is it that I even have to ask these questions?

[Keith Patton]

This is amazing. The question was asked 2 years ago. I will be switching to GitHub because the support is incredibly poor.

[yegor.k]

WTF?!

Is this the official answer?

So, Atlassian doesn't understand a thing about user management. Should I trust them with my projects??

[Anthony Erbe]

I will throw my hat in the ring too. Not being able to find the correct bb username/email has been an issue multiple times now. We have users that come on the team that had prior bb accounts and jira accounts and tracking down which user/email they used is a nightmare.

[Bejoy John]

This is absurd and ridiculous and potentially puts companies' proprietary data at risk of ex-employees! Please make this change or else there are enough other providers who have a better understanding of GDPR!

https://rushabhshah065.medium.com/lets-move-repository-from-bitbucket-to-github-with-all-branches-and-commits-f93c7d3bda67

[spryce]

It's hard to understand the reasoning for this behaviour. Hopefully this feature can be provided soon.

[mac_nsr]

Logged in just to say: it's 2023 and this is still ridiculous. Yes, I can export the csv and get the email addresses that way -- but why should I have to do that, and how would I know to expect it when the email addresses don't appear in the UI?!

[Jan Bauer]

The only feasible way I found is cloning the repo from BitBucket and run "git log". That shows the email addresses of each commit, as configured in the ~/.gitconfig of the user who made the commit.

But no chance to show emails in the BitBucket UI, same as git tag descriptions and commit signing. git supports it, but BitBucket is not really git compatible.