Can you show a sample URL that demonstrates your problem?
Normally, a PR is available under a URL like this:
https://bitbucket.org/foobar/baz/pull-requests/123
... where "foobar" is the workspace slug, "123" is the PR ID. Both are global, not personal.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Anton - Can you share some screenshots?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
e.g. in jira PR is referenced like https://bitbucket.org/%7B8b57baea-ae50-4078-8bfc-d0c0fb51dc09%7D/%7B11451fec-edef-41d5-8ecc-dd53c0b4547d%7D/pull-requests/8911 and other team members can not access it, just me.
While it's actual url, accessible by everyone with proper permissions, is https: / /bitbucket.org/organization/repository/pull-requests/8911
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just to clarify - we are not Atlassian support. We are just end users like you, so we do not have access to your Atlassian site to see things. That's why you need to post screenshots.
So, based on what you have posted, it looks like it might be related in how you came into the work item. Is your process that you arrived at a work item from somewhere and then clicked on the link in the Work Item?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi! I'm browsing work item in Jira, on right sidepanel there is "Development" section, which shows PRs, branches and commits of associated Bitbucket repository. Links shown in this section uses kind of personalized urls involving unique ids, it is kept even when I navigate and subnavigate it. So I can't share URL of PR, commit, comment etc if I came to Bitbucket via such link, instead, when I want to, I have to open Bitbucket directly, find the same PR or commit or file in corresponding workspace, then share regular-style URL.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You said you were browsing work item - what does that mean? Did you come to the work item from a filter, for example? Or did you query the work item directly in the search box? How did you get to the work item and what does the URL look like?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I use direct work item link like https://**.atlassian.net/browse/**-7831 (from e.g. project board) and from-filter links like https://**.atlassian.net/issues?filter=**&jql=**&selectedIssue=**-7831. Does not affect how Bitbucket URLs are formed in Development sidepanel section, it is always sanitized/personalized, not direct links to PRs.
It is some recent weeks or months change, previously I saw direct links here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Very good - thanks for that information. You should go ahead and open a support ticket with Atlassian in my opinion to find out what is going on. Please post back here with the solution/advice for future readers. Best of luck!
https://support.atlassian.com/contact/#/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We'll need access to your workspace to view the URL's you're talking about (which wouldn't be appropriate to share in a public forum such as community).
Given that you belong to a paid workspace, I'll go ahead and raise a support ticket on your behalf. May I know what your timezone is so I may raise it with the correct team who works within your timezone?
Cheers!
- Ben (Bitbucket Cloud Support)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Noting here that we have the same issue. Jira essentially obfuscates the links with random-ids instead of the repo name, etc. This used to not be the case.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.