Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
Severity 3 - Minor
-
61
-
3
-
Description
Issue Summary
On Chrome, if you keep third-party cookies disabled and click on a Jira Issue from Commit messages, Pull Requests etc, the expected behaviour is to open in a pop-up. However, it does not open and shows an error message that says there is no access for the user.
There is a problem with third-party cookies. Most browsers are disabling them completely with no workarounds. Asking customers to enable them is only a bandaid fix. You can find Google's Announcement here.
There was also a similar issue with Safari where cross-site requests were causing the issue and the fix was to open the links in a new tab - BCLOUD-17536.
I also found a very similar issue with Firefox - BCLOUD-21921 where I believe the cause is the same because I analyzed HAR files of when the ticket was blocked on Firefox and Chrome and I noticed that the same request was being blocked on both Browsers. On firefox, the workaround was to disable "Enhanced Protection".
Steps to Reproduce
- Turn off third-party cookies in Chrome Settings
- Go to any Repository on Bitbucket with a Jira key in the commit message or pull request.
- Click on the key
Expected Results
The Jira issue should open in a pop-up within the page itself
Actual Results
An error message is shown that says the user has no access
Workaround
- The obvious workaround is to enable third-party cookies
- Ctrl/CMD click on the issue so that it opens in a new page
Attachments
Issue Links
- is related to
-
BCLOUD-17536 On the Safari browser, Bitbucket is not able to link to the Jira issue from the Bitbucket PR.
- Closed
-
BCLOUD-21921 Clicking Jira issue key on Firefox does not load details
- Gathering Impact