-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PR Harmony 2.3.1 compatibility with Bitbucket 4.3.2 #46
Comments
I've tested with that Bitbucket version (and just retested for sanity) without issue, so I don't think this is a compatibility problem. Can you share your browser version, the URL of your Bitbucket server, and the output of your browser console when you try to save the page? I suspect that there's an environment issue here. |
My browser is google chrome and version is Version 50.0.2661.102 m Please note I used PR Harmony version 2.2.0 for this test since I had the same issue with the latest version as well. If you want I can use the latest version. Console Output is as follows: DEPRECATED JS - Cookie has been deprecated since 5.8.0 and will be removed in a future release. Use cookie instead. |
Any findings, please share. |
It doesn't look like anything stands out in your environment. However, if your username has a capital letter in it there was a bug fixed in PR Harmony 2.3.1 to allow correct saves. Might be worth trying out that version. |
I tried with PR 2.3.1 as well. Getting similar issue. |
I'm using PR Harmony 2.3.1 with bitbucket server v4.10.1. I notice in IE11, the default reviewer group are not added at p/r creation even though a default review group is set/saved. But this issue is fine in FireFox and Chrome. IE Compatibility setting seems like is not the culprit. My username is all cap. Thought? Thanks. |
I am using Bitbucket 4.3.2 and installed PR Harmony 2.3.1. But when I tried to configure PR Harmony for one of the Repo and click on Save button. I found that it saved nothing. And even when I created PR, there was nothing (no default reviewer, no required approver etc.)
Whereas there is an exception for local bitbucket users. It seemed to work for local users.
The text was updated successfully, but these errors were encountered: