Back
All posts

Bitbucket Slack channel and hook overrides using patterns

April 24, 2026
<a href="https://www.freepik.com/free-vector/business-team-brainstorm-idea-lightbulb-from-jigsaw-working-team-collaboration-enterprise-cooperation-colleagues-mutual-assistance-concept-pinkish-coral-bluevector-isolated-illustration_11667116.htm#query=collaboration&position=2&from_view=keyword&track=sph&uuid=21ea3c1d-7461-49c7-9157-5822c4372896">Image by vectorjuice</a> on Freepik

Check out Bitbucket Slack integration video demo.

Question

I am integrating Bitbucket Data Center and Slack. I am trying to set up Slack notifications using the pattern option wherein all the Bitbucket pull requests to master should go to one Slack channel, and pull requests to bugfix should go to another channel. I am using this pattern master->#bb-master,bugfix->#bb-bug-prs


Answer

The setup is pretty easy to achieve this. The main issue here is to understand the source (from) and destination (to) branches.


The source branch is where you have your source code, and the destination branch is where you want to merge your pull request. In the question above, you create a bug pull request with a destination branch bugfix. You create pull requests with the master as a destination when you want to merge there.


Let us show you how to set this up with App "Slack notifications for Bitbucket" by Move Work Forward.

Our initial setup is that we have 2 Slack channels - #bb-master for the pull requests with the master branch as a destination and #bb-bug-prs for the Bitbucket pull requests for the bug fixes. We usually name those bugfix/DEV-123-bug-description, where DEV-123 is the Jira issue key.

Afterwards, we create an Incoming Webhook for the #bb-master branch only.

We configure a repository config with the following pattern master->#bb-master,bugfix->#bb-bug-prs.

After we configured the rule we created 2 Bitbucket pull requests: one against the master and another against the bugfix branch.

When the pull requests created or merged the corresponding Slack channels will get notified.

Important: You need to pay close attention when to use From branch or To branch setting.

Try our Slack notifications for Bitbucket App. Please reach out if you have any questions or doubts.

Articles you might like

Atlassian announces a new partnership with Slack
April 24, 2026
Atlassian announces a new partnership with Slack
Atlassian has made an equity investment in Slack, and Slack has acquired the IP for Stride and HipChat Cloud. Slack has been a user of Atlassian products for many years, and Atlassian's employees are using Slack now. Microsoft Teams is an option as well.
Read more >
Automate Project Builds Using a Parametrised Jenkins Pipeline in Bitbucket Server
April 24, 2026
Automate Project Builds Using a Parametrised Jenkins Pipeline in Bitbucket Server
Streamline workflows with our step-by-step guide on integrating Bitbucket Server with Jenkins Pipelines. Improve collaboration & efficiency with our app now!
Read more >

Articles you might like

New blog posts

The Compass Alternative for Small Teams: DORA-Style Delivery Metrics Right Inside Confluence
June 17, 2026
The Compass Alternative for Small Teams: DORA-Style Delivery Metrics Right Inside Confluence
Atlassian Compass is moving to DX. Here's how SMB and mid-market engineering teams keep DORA-style delivery metrics - PR cycle time, throughput, and review latency - live inside Confluence, included in GitHub Links for Confluence, with no code or PR data stored.
Read more >
5 Apps from Connect to Forge in 2 Months: What We Learned
June 17, 2026
5 Apps from Connect to Forge in 2 Months: What We Learned
We moved five of our Atlassian Marketplace apps from Connect to Forge in two months. Here's how we did it, the gotchas we hit, and what we got out of it.
Read more >
Jira Notifications in Microsoft Teams Not Working? Fixes + a Permanent Solution (2026)
June 15, 2026
Jira Notifications in Microsoft Teams Not Working? Fixes + a Permanent Solution (2026)
Jira notifications stopped appearing in Microsoft Teams? The five most common causes — broken OAuth, private channels, webhook errors, noisy defaults, missing filters — with fixes for each, plus the Native-Plus Rule for deciding when the free native app is no longer enough.
Read more >
Get productivity tips delivered straight to your inbox
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Atlassian Logo
Platinum Marketplace Partner
AICPA Logo
SOC 2 Type II Certified
Gitlab Logo
GitLab Official partner
EU GDPR Logo
EU GDPR Compliant
Google Logo
Google Partner
Microsoft Logo
Microsoft Partner