Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Transitioning BitBucket issue with a commit message not working


I'm trying to understand how this works

For I create an issue in BitBucket Cloud, and it has issue #3 with status of open.

I then create a branch

git checkout -b my-issue-3-branch

make some edits and then I make a commit with

git commit -a

and add the comment at the top with

Updates for fix issue #3

I then push the code to remote with

git push -u origin my-issue-3-branch

I can see the commit for the branch, and I can see #3 is linked to issue #3.

According to the documentation, this should transition the issue to a Resolved state and add a comment that matched the commit.

But it doesn't.

Wat am I missing? (It's possible I've skipped a step, but I've donethis a fwe times with commits, and I can't get issues to transition.

4 answers

Well, this is still occurring for me. I can see in the commit comment that Bitbucket has linked #11 to the correct issue. But it doesn't transition.

Kinda annoying.

I have the same problem.

Scenario 1:

Bitbucket > Issues tracker (in a repository on which I have Write access)

Push with "close issue #" in commit > Creates commit with linked issue in Bitbucket > Does NOT add comment to the issue > Does NOT close the issue


Scenario 2:

Bitbucket > Issues tracker (in a repository on which I am Admin)

Push with "close issue #" in commit > Creates commit with linked issue in Bitbucket > Does add comment to the issue > Does close the issue


Anyone? ... Anyone?

Hmm, I'm the admin for my repo, so I'm not sure what is different between what we're seeing.

I can't find a project on to look if this has been reported.

I just noticed that the difference appears to be more related to whether the repository was forked or not. In my scenario 1, the repository is forked (and commit commands do not work). In my scenario 2, the repository is not forked (and commit commands do work). 

Hmmm, my repo isn't forked.

I too have this problem. The issue is never transitioned to a Resolved state. It works for another account (and repository).

0 votes

Hi Jim,

It appears you didn't put the transition in your push.  The format should be as follows according to Using Smart Commits in Bitbucket Server:

<ignored text> ISSUE_KEY <ignored text> #<transition_name> <comment_string>

The example from is as follows:

JRA-090 #close Fixed this today



Hi Brandon,

Thanks, but the page you linked to is when JIRA is linked to BitBucket Cloud and you're using Smart Commits, which is a different feature.

I don't have JIRA, I only have a BitBucket iIssue I'm trying to transition with a git commit as documented in


What insane person formats commits like

JRA-090 #close Fixed this today

Well, even if I did, still doesn't work. The issue is linked, but nothing is transitioned to DONE.


I'd much rather have this format work:

Fixed this today

Closes JRA-090


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

2,214 views 2 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you