See the Project Settings - Notification Policies and Repository Settings - Notification Policies for creating, deleting and editing notification policies.
Bitbucket has a complete event subsystem that fires events whenever anything happens inside the application. For example, a an event is fired whenever a repository branch is created or a pull request is merged.
To notify Mattermost from Bitbucket when a repository branch is created, your Bitbucket Administrator will set up the correct policy. Then, when a repository branch is created from in a repository in Bitbucket, the designated Mattermost channel will receive a notification.
Example:
A Bitbucket user creates a branch in the repository namedXXXApolloUI. This repository belongs to the project Team. This project has, for its project channels, the Mattermost channel XXXBitbucket. With a "Repository Createdbranch created" notification policy set for the project, the following notification would be seen in the XXX Bitbucket channel upon repository branch creation:
The date/time of creation are shown. The notification shows the issue type, reporter, assignee, priority, status and resolution status. was created by the user in JIRA. A link is provided to the issue in JIRABitbucket project (Team), the repository (ApolloUI) and the name of the branch (adam).
Links to Bitbucket are provided for team, repository and branch.
Here are the results in Mattermost for the different notifications:
Issue Created
Issue Updated - Priority changed.
Repository Events | |
---|---|
Code pushed | |
Branch created | |
Branch deleted | |
Pull Request Events | |
Opened | |
Commented | |
Declined | |
Deleted | |
Merged | |
Reopened | |
Reviewed | |
Approved | |
Unapproved | |
Updated |