Configuring @mentions
Mentions gives Atlas an ability to directly notify users that something need their attention. It can be a pull requests that need to be reviewed by them or a build that has failed for their changes (commits).
Atlas is trying to use mentions only when it matters, so if an user causes an action - he won't be mentioned, examples:
Creator of a pull request want be mentioned because he knows that a card with new pull request will be presented by @Atlas.
When pushing changes to a repository - author or a commit on which build will start wont be mentioned.
See an example below:
Link-like mentions - they leads to Bitbucket profiles.
Mentions of other users - they should be notified by Hangouts Chat about unread message.
Mentionss of you
See other example:
Link-like mentions.
Normal mentions.
When bot mentions you - you may have notification about unread message from your Hangouts Chat app (it depends on your app settings). Also, the unread message badge will appear in specific chat rooms:
Linking Hangouts Chat user account with Bitbucket Cloud account
@Atlas does not know how to properly recognize users from Bitbucket in Hangouts Chat room unless each user will connect both Hangouts Chat and Bitbucket/Atlassian accounts.
If a particular user wants to be mentioned, then he should login to Bitbucket from the chat (any room or private chat with Atlas will be good).
Lets accomplish this by typing:
@Atlas login bitbucket
Then, you will be presented a card to configure mapping.
Â
After clicking a link Configure you will be presented an authorization page within Bitbucket. Accept a scope and choose appropriate Bitbucket account - it should be the account you want be mentioned in chats.
You may map as many Bitbucket accounts as you want. You may also map specific Bitbucket account with many Hangouts Chat accounts this way.
Bitbucket server support is not yet implemented. We plan to add mentioning for Bitbucket server in 2Q2020.
Mentions will be free on all plans until May 30. After May 30 it will be available on Standard (not Basic) plans.
Â