UUID in link to pull request instead of repository name

[Devesh Khandelwal]

In the related commits, pull requests and branches, I'm seeing the UUID instead of the repo name in the URLs.

Example:

https://bitbucket.org/%7B%7D/%7B76d712f5-6724-4604-a610-405b6bdcacfd%7D/commits/2daf0fa3b6dabed75349cc41cc83073c00b2b670

Is this a known bug? Anyone else also facing this?

[seanaty · Accepted solution]

Is this a bug? Is the link not working for you?

Bitbucket links work with both UUID and account name. As part of GDPR work, we've been working remove usernames where possible. Read here for more details:

https://developer.atlassian.com/cloud/bitbucket/bitbucket-api-changes-gdpr/

If you urldecode that path you'll see https://bitbucket.org/{}/{76d712f5-6724-4604-a610-405b6bdcacfd}/commits/2daf0fa3b6dabed75349cc41cc83073c00b2b670

Here the repository is being referenced by the repository UUID and therefore the account username or UUID is unnecessary so it's just `{}`.

If this link _isn't_ taking you to the commit page, that is certainly a bug.

[Devesh Khandelwal]

The links certainly work, but I just thought that it's a bug since it only happens when going to a PR/commit/branch from JIRA, and not bitbucket itself.

Does this mean this is how it's going to be in the future? In my opinion, it's a little inefficient because earlier, by just seeing the URL, we were able to tell which repo it is, which was very useful in guessing URLs, and in cases where there are multiple PRs associated with a Jira ticket.

And, additionally, the repo name based URL structure seemed cleaner. I understand the concerns around user privacy, but with repo names, I'm unable to see what is the motivation behind this.

[seanaty]

I'll raise this issue with the responsible development team. The motivation is really an attempt at scrubbing usernames, considered personal data, from Bitbucket and all of the many different services built on top of it. It however, will be replaced with a different type of container that isn't considered personal data and that can ultimately be used to provide a better reference. I think the UUIDs in the URLs were just an interim solution.

[Nessa Hood]

Are repo names even PII? For our links we have the company username instead of the initial /{}/.

Overall this has been annoying me for a while too. Could you at least make the UUID version redirect to the clean url so copy and paste will be nicer?

[seanaty]

Since this came up in another thread, I'm posting the public issue here: https://jira.atlassian.com/browse/BCLOUD-20811

Voting/watching this issue there will increase the chances this gets worked on.