Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Disable new Merge button that appears in the Jira integration

Kent Muller
Contributor
February 26, 2025

Recently a new Merge button has started appearing in the Development section in Jira issues where there is an associated feature branch in Bitbucket.

The button appears late, a number of seconds after the issue has loaded and as a result the entire view moves down and instead of clicking to view a pull request, you end up clicking Merge.

How can we remove this Merge option, but leave the previous Branch, Commits, Pull Request options in place?

5 answers

1 accepted

3 votes
Answer accepted
Rasmus
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 5, 2025

There is a related Issue raised for the Jira Cloud Project you can upvote/follow:
https://jira.atlassian.com/browse/JRACLOUD-93484

Kent Muller
Contributor
March 5, 2025

Thanks for posting this. I would encourage anyone seeing this to upvote this issue.

2 votes
Richard Bostock
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 28, 2025

You can disable it in your personal settings. It's provided by Jira Labs.

 

I similarly found that it was very easy to click on this when I was trying to follow the link to the PR itself whilst the page was still loading... 

 

Screenshot from 2025-02-28 14-53-02.png

Kent Muller
Contributor
March 4, 2025

Thanks for the tip however this didn't work for me unfortunately. The Merge button still appears after a short period.

Richard Bostock
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 13, 2025

I found this worked for a day or so and then the button sadly reappeared. I've joined the others on adding to the registered issue shown above.

0 votes
Kent Muller
Contributor
March 13, 2025

It looks as though changes have been made and the Merge button is now appearing below the existing links so when it loads late, the regular links aren't being pushed down anymore.

0 votes
jorcutt
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 4, 2025

The number of accidental merges this created in a short period of time for us is crazy.  Developers move fast and having a UI that shifts with a merge option that appears exactly where another link was displaying is silly.  If this take a long time, put in a skeleton and reserve the real estate so that people don't accidentally click on it.

 

We are recommending that everyone disable the new transition experience in our organization.

0 votes
Fabio Racobaldo _Herzum_
Community Champion
February 28, 2025

Hi @Kent Muller and welcome,

for my knowledge, you can't disable that specific button. It will appear for users that have write permission on the linked repo on bitbucket side. It is an useful feature for developers.

Hope this helps,

Fabio

Kent Muller
Contributor
March 4, 2025

Thanks for you response.

While it may be a useful feature, having it load late is the issue here.

The space should either be reserved so the UI doesn't move after loading, or the entire section shouldn't load at all until everything is ready.

Developers are streamlined and focussed. Having a UI that is slow to catch up to the human makes for an undesirable user experience.

Shaun Dishman
Contributor
March 4, 2025

It is an useful feature for developers

 

I am a developer, and it is the opposite of useful; it caused me a MAJOR headache today by breaking our builds and causing me to interrupt planned work to go fix what Jira screwed up.

It might be useful, if it was implemented with sensibility, but some mind-boggling decisions were made here:

  • It merges all PRs associated with the issue - even ones that are not yet approved!
  • There is not even a confirmation for such a drastic action

 

This is easily the worst, most regressive capability I've seen added to Jira in the 10+ years we've been using it.

Like # people like this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin Site Admin
TAGS
AUG Leaders

Atlassian Community Events