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?
There is a related Issue raised for the Jira Cloud Project you can upvote/follow:
https://jira.atlassian.com/browse/JRACLOUD-93484
Thanks for posting this. I would encourage anyone seeing this to upvote this issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the tip however this didn't work for me unfortunately. The Merge button still appears after a short period.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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:
This is easily the worst, most regressive capability I've seen added to Jira in the 10+ years we've been using it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Spend the day sharpening your skills in Atlassian Cloud Organization Admin or Jira Administration, then take the exam onsite. Already ready? Take one - or more - of 12 different certification exams while you’re in Anaheim at Team' 25.
Learn more
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.