Auto-close on merge chooses CLOSED status not DONE

[Carl-Erik Kopseng]

• We have both the status Closed and Done in our JIRA workflow. Closed is used for discarded tasks or stuff that is duplicated, etc.

Previously we just had Done and the option to close an issue when a merge is performed would automatically set the right status. Now that there are two statuses that both signify "Done", Bitbucket chooses the first one (by alphabetic sorting?), which unfortunately is Closed, not Done.

I see no way of changing this default, but maybe there is?

[Ben]

Hi @Carl-Erik Kopseng 

Unfortunately, there's no option to toggle which transition is chosen by default.

For full transparency, a feature request to include this will not be looked into by our developers - as we are sunsetting issues shortly:

• https://community.atlassian.com/forums/Bitbucket-articles/Announcing-sunset-of-Bitbucket-Issues-and-Wikis/ba-p/3193882

I'd suggest switching over to JIRA for issue management, or:

• Turn off the “close on merge” behaviour and:

  • Either close issues manually to the correct status after the PR is merged, or

  • Use commit messages and commands to drive transitions (see: https://support.atlassian.com/bitbucket-cloud/docs/resolve-issues-automatically-when-users-push-code/).

Cheers!

- Ben (Bitbucket Cloud Support)

[Carl-Erik Kopseng]

We are using Jira and this was about the option to close a Jira ticket. 

I was unaware there even existed an issue tracking system in Bitbucket.

[Ben]

Hi @Carl-Erik Kopseng ahh my apologies, I misunderstood.

When a Bitbucket Cloud PR is merged, Bitbucket just sends an event to Jira rather than deciding which status it's transitioned to (that is handled on the JIRA side). 

In your case, because the workflow has both Closed and Done as terminal statuses, the current rule/transition that runs on PR merge is targeting Closed.

There’s still no Bitbucket setting to change that default, but you can fix it in Jira by:

• Editing the Jira Automation rule (or workflow trigger) that runs “on PR merged”, and

• Changing the transition so it explicitly moves the issue to the Done status rather than Closed.

Once that’s updated, merging a PR will move linked issues to Done again, even though Closed remains available for duplicates / discarded work:

• https://support.atlassian.com/jira/kb/transition-jira-issue-when-bitbucket-pr-is-approved/

If this still doesn't resolve your issue, please raise a ticket directly with our support team using your paid workspaceURL (bitbucket.org/{workspaceID} ) - as we'll need access to your workspace/JIRA instance to troubleshoot further (this requires a ticket):

• https://support.atlassian.com/contact/

If you have issues raising a ticket, please let me know your timezone so I may raise one on your behalf with the team who operates within your working hours.

Cheers!

- Ben (Bitbucket Cloud Support)