Merge Button is disabled(grayed out) even there is no conflicts.
Asked by deepan:

Hi .,

From today morning We are facing issue Merge Button is disabled(grayed out) even there is no conflicts in pull requests.

Please help me out in resolving this Issue. we are facing issue in merging the pull request because of this.

![Screenshot 2020-11-23 at 9.46.31 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/119259iC6FC60CB1FF2F3A7/image-size/large?v=v2&px=999 "Screenshot 2020-11-23 at 9.46.31 AM.png")


Answers:
author: shawnlegge
body: We found a quick fix for this by disabling new pull requests experiences in <https://bitbucket.org/account/settings/features/>

comments: author: waleems
body: Great!.. Thanks


author: deepan
body: [@shawnlegge](/t5/user/viewprofilepage/user-id/3161286)Its already disabled in my account. also tried enable and disable new pull requests experiences but didn't work for me. still same issue.


author: waleems
body: You need to enable the "New pull request experience" in <https://bitbucket.org/account/settings/features/> and make sure the merge strategies in your repo settings is "Fast Forward". After that you will be able to merge the PR![Screen Shot 2020-11-23 at 5.00.21 pm.png](https://community.atlassian.com/t5/image/serverpage/image-id/119272i881C5810C05B6999/image-size/large?v=v2&px=999 "Screen Shot 2020-11-23 at 5.00.21 pm.png")![Screen Shot 2020-11-23 at 5.06.12 pm.png](https://community.atlassian.com/t5/image/serverpage/image-id/119273i91B5914352AC5D86/image-size/large?v=v2&px=999 "Screen Shot 2020-11-23 at 5.06.12 pm.png")


author: deepan
body: thanks ! its works


author: Jimmy Seddon
body: Hi [@deepan](/t5/user/viewprofilepage/user-id/2927601),

If you hover over the merge button, does it give you any information about why it is grayed out? The most common items other than conflicts that will prevent this are [branch permissions](https://support.atlassian.com/bitbucket-cloud/docs/use-branch-permissions/) or [merge checks](https://support.atlassian.com/bitbucket-cloud/docs/suggest-or-require-checks-before-a-merge/) (which are only relevant to premium subscriptions).

I hope that helps!

-Jimmy

comments: author: Pak Woon
body: I have the same issue. Nothing appears when you mouse over the button.

Edit: Using Firefox 83.0 (64-bit) on Ubuntu 16.04.


author: deepan
body: Hi [@Jimmy Seddon](/t5/user/viewprofilepage/user-id/512822)

Nothing appears when you mouse over the button. no information or error.

i just want to clarify there is no merge conflicts or branch permission issue at all.

all pr's has same issues.


author: Jimmy Seddon
body: [@deepan](/t5/user/viewprofilepage/user-id/2927601) I just created a test PR in a free instance I own, and it looks like I can see the same thing but only when using the "Old Pull Request Experience". I think what you are running into is this: <https://jira.atlassian.com/browse/BCLOUD-20079>

The workaround is to turn on the "New Pull Request Experience" in the Labs section of your account, which you should be able to access from here: <https://bitbucket.org/account/settings/features/>

I hope that helps!

-Jimmy


author: Pak Woon
body: [@Jimmy Seddon](/t5/user/viewprofilepage/user-id/512822)This worked for me. Thanks for your help


author: deepan
body: [@Jimmy Seddon](/t5/user/viewprofilepage/user-id/512822)Thanks its works!


author: Jimmy Seddon
body: [@deepan](/t5/user/viewprofilepage/user-id/2927601) [@waleems](/t5/user/viewprofilepage/user-id/4170186) [@Pak Woon](/t5/user/viewprofilepage/user-id/1474366) [@shawnlegge](/t5/user/viewprofilepage/user-id/3161286) I would encourage each of you to go and vote/comment on this bug: <https://jira.atlassian.com/browse/BCLOUD-20079>

Having more customers indicate it affects them my help get Atlassian to fix the bug sooner.

-Jimmy


author: shawnlegge
body: We are having a similar issue

comments: author: deepan
body: [@shawnlegge](/t5/user/viewprofilepage/user-id/3161286)Thanks for put it here.


author: waleems
body: We are facing the same issue, we had never faced this issue before. Would glad if someone solved this...


Tags: bitbucket-cloud

cloud