Mark up comments

You can refer to a Bitbucket Cloud issues, requests, and users directly from a comment an issue or a commit message.  When you create a reference, saving the comment (or issue) causes Bitbucket to automatically link to that object.  You can also mention an individual, or even insert an emoji. 

For items that are repository-specific, such as issues, pull requests, and commits, references to Bitbucket objects always refer to the current repository.  For example, when commenting on a pull request in repoAlpha you can't link to an issue in repoBeta.  

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

If you want to add special formatting such as headings and code references, you can use any supported Markdown syntax in any comment. 


We support the following extensions for  Python-Markdown codehilite, tables, def_list, del, footnotes, headerid, sane_lists, abbr, fenced_code, toc, wikilinks.

We don't support arbitrary HTML in Markdown, for example <table> tags.

Linking to Bitbucket Objects from Comments and Commit Messages

Issue

Syntax : issue #number

Links to a given issue. Supports the following arguments:

Argument Description Required?
number The issue number Yes

You can also close or reopen issues by including specific keywords in your commit messages, for information about Resolve issues automatically when users push code.

Examples:

issue #88

Results in the following output:

issue #88

Pull request

Syntax : pull request #number

Links to a given pull request. Supports the following arguments:

Argument Description Required?
number The request number Yes

Examples:

pull request #1541

Results in the following output:

pull request #1541

Changeset

Syntax:  HEX_CHARS

Links to the given changeset. The system links any changeset hash automatically also.  Supports the following arguments:

Argument

Description

Required?

hashvalue A changeset hash. Yes

Examples:

9cc27f2

User mentions 

Syntax:  @name 

In order to respect and continue to improve user privacy, Bitbucket Cloud is changing the way we serialize user mentions, which impacts how a user’s name appears prior to saving your updates or changes for snippet comments and pull request descriptions or comments in Markdown. Now when you are mentioning a user, you’ll see their Atlassian account ID next to their name. 

Supports the following arguments:

Argument

Description

Required?

name The name of the individual user. Yes

Example:

@Joe Smith will look like the following prior to saving your updates or changes: @[Joe Smith](account_id:123456:w8eid84j-2bda-4f1f-85c8-9bf264e966ac)

Emoji

Syntax:  :emoji:

Displays the given emoji.  We don't have a definitive list of supported emoji; you'll need to just test the emoji you want to use. One of our users, David Coffey, created a list of available emojis

This syntax supports the following arguments:

Argument

Description

Required?

emoji The name of the emoji. Yes

Examples:

:mask:

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 .



Last modified on May 7, 2019

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.