How to consistently link a git commit comment to a Bitbucket Cloud issue? Edited

When attempting to link a git commit comment to a Bitbucket Cloud issue why does "issue #number" not update the issue comments where "see #number" does?

examples:

a) git commit -m "issue #345 - Lorem ipsum dolor sit amet"

b) git commit -m "see #345 - Lorem ipsum dolor sit amet""

 

I see both (a) and (b) create a "link" back to the commit however only (b) creates the comment in the issue.

 

I've reviewed the following 2 articles and it does not help in understand the inconsistency... 

Mark up comments, issues, and commit messages

Resolve issues automatically when users push code

0 answers

Suggest an answer

Log in or Join to answer
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

710 views 0 4
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot