Mark up comments

Bitbucket Cloud allows you to use Markdown syntax any place in the user interface where you can enter a comment.  For example, line commenting, pull request comments and change set comments.  You can also use Markdown when creating issues on the issue tracker. There are also some special things you can do like link to external websites or Bitbucket issues and pull requests — and a lot more.  

For a tutorial Bitbucket's Markdown support, including syntax examples, see our Markdown demo repository.

We support Python-Markdown. Please note, we don't support arbitrary HTML in Markdown, for example <table> tags. Instead, we use safe mode. Safe mode requires that you replace, remove, or escape HTML tags appropriately.

A short peek at Markdown in action

Markdown syntax allows you to create some fancy comments. You can type Markdown by hand or use our comment bar:

Linking to Bitbucket Objects from Comments and Commit Messages

You can also refer to a Bitbucket issues, requests, and users directly from a comment or issue or commit message.  When you create a reference, saving the comment (or issue) causes Bitbucket to automatically link to that object.  For items that relate to a repo, such as issues, pull requests, and commits, markdown references to Bitbucket objects always refer to the current repository.  You can also mention an individual or team account — even insert an emoji.

Linking to objects for comments and issues within a repository
Object Syntax Example
pull request
pull request #PR_NUMBER
pull request #29
issue #3


7-40 chars

Linking to non-repository objects
Object Syntax Example
user (account)


David Coffey created a list of available emoji.  


Finally, if you have created a link to JIRA Software or another service such as Jenkins, you can enter references for those "linkers" too.  For information on creating and using linkers, see Link to a web service.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport