Create a Bitbucket branch for a Zendesk bug
Move from confirmed customer bug to a ready branch in one step.
Trigger
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
Action
Create a branch
Creates a new branch in a bitbucket repository from a target commit hash; the branch name must be unique, adhere to bitbucket's naming conventions, and not include the 'refs/heads/' prefix.
Why this helps
Engineers lose time preparing branches before they can investigate a customer issue.
- Shorten time to investigation
- Use consistent branch names
- Keep branch origin traceable
Setup
Build it in a few focused steps.
- 1Connect Zendesk and Bitbucket once.
- 2Create a bug triage automation.
- 3Tell Notis to create a uniquely named Bitbucket branch from the target commit for each confirmed bug ticket, including the ticket ID in the name.
- 4Choose the New Zendesk Ticket trigger and report channel.
- 5Test with a reproducible bug ticket and a supplied repository and commit.
Questions about this workflow
What does Notis need to create a branch?
Provide the Bitbucket workspace, repository, target commit hash, and branch naming rule.
Can the branch name include the ticket number?
Yes. Ask Notis to include the Zendesk ticket ID while following Bitbucket naming rules.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Zendesk to Bitbucket. A trigger fires from one place; an action lands in another.
Zendesk triggers
Bitbucket actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create a branch
Creates a new branch in a bitbucket repository from a target commit hash; the branch name must be unique, adhere to bitbucket's naming conventions, and not include the 'refs/heads/' prefix.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create an issue
Creates a new issue in a bitbucket repository, setting the authenticated user as reporter; ensures assignee (if provided) has repository access, and that any specified milestone, version, or component ids exist.
New User Created
Triggered when a new user is created in Zendesk.
Create an issue comment
Adds a new comment with markdown support to an existing bitbucket issue.
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
Create a pull request
Creates a new pull request in a specified bitbucket repository, ensuring the source branch exists and is distinct from the (optional) destination branch.
Create repository
Creates a new bitbucket 'git' repository in a specified workspace, defaulting to the workspace's oldest project if `project key` is not provided.
Create snippet comment
Posts a new top-level comment or a threaded reply to an existing comment on a specified bitbucket snippet.
Delete issue
Permanently deletes a specific issue, identified by its `issue id`, from the repository specified by `repo slug` within the given `workspace`.
Delete repository
Permanently deletes a specified bitbucket repository; this action is irreversible and does not affect forks.
Connect any two apps with Notis in the middle.
Zendesk and Bitbucket, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Bitbucket.