How to stop Jira from closing issues when merging a Bitbucket Pull Request?

[Manuel W_]

Hi all,

we're using Jira v8.13 and have set it up in a way so we can create BitBucket branches and Pull Requests from within Jira.

Everytime someone closes a Pull Request, the issue gets set to "done". This is one of two final states we have, "done" and "wontfix".

How can I stop Jira doing that?

Often, there are more than one Pull Requests linked to one issue. Currently I have to re-open the issue after every Pull Request merge, which is very annoying.

Thanks,

Manuel

P.S.: I'd like to add that I'm the Jira admin. But I feel very overwhelmed by the amount of configurability there is. I'm a software dev who now takes care about Jira on the side.

[Sümeye Beki]

Hi @Manuel W_ 

Jira or Bitbucket does not do this by itself unless you say so. There may be triggers on the workflow. Could you please check the workflow transition's trigger tab? 

[Manuel W_]

Hi @Sümeye Beki

I did so -- the workflow transition has no trigger set.

[Sümeye Beki]

Hmm, then, could you please check your Bitbucket repo for webhooks? Or you may, idk, have post function on your CI tool(Jenkins etc)

[Manuel W_]

Hi @Sümeye Beki,

I checked BitBake but we don't have any WebHooks active.

This is what shows up in a Jira issues activity tab when a pull request closes the issue:

Automated transition changed the status to Done on BLY-2346 - Headline goes here (triggered when Manuel merged pull request #721 in Bitbucket)

Does that give an indication on what triggers it? The projects workflow is "Software Simplified Workflow for Project BLY" with a note "Generated by JIRA Software version 8.5.0-DAILY20190920183006. This workflow is managed internally by Jira Software. Do not manually modify this workflow."

I checked the workflow steps and found a transition "successful review" on the "Ready For Review" step...

 but it has no triggers assigned. This is likely the transition triggered when clicking the "successful review" button in the GUI.

[Sümeye Beki]

The projects workflow is "Software Simplified Workflow for Project BLY" but also the issue that is triggered via pull request is using this workflow, right?

[Manuel W_]

Yes it is! Just checked. That's the only workflow active for this project and all issue types are assigned to it.

[Sümeye Beki]

Okay, what about listeners or Automation for jira plugin? There may be a listener or automation rule for the issue.

[Manuel W_]

@Sümeye Beki I will look into this asap, which won't be earlier than in a few days I'm afraid. I very much appreciate your help and will give notice when I was able to check.

[Manuel W_]

@Sümeye Beki I now checked and can confirm we haven't got any custom listeners (only non-configuratble Jira-internal ones) set up. Also "automation rule". I think Jira Automation got added only later and our Jira 8 doesn't yet support it as I couldn't find anything hinting at that feature.

I found an "Application Link" between BitBucket and Jira with a feature "Smart Commit". I disabled it but it didn't change anything.