Create release branches from a request
Turn a release or hotfix request into a uniquely named branch from the commit it identifies.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Release preparation slows down when branch creation details are scattered across requests and someone has to set them up manually.
- Start release preparation from a standard request.
- Use the target commit supplied with the request.
- Cut down manual branch setup and naming errors.
Setup
Build it in a few focused steps.
- 1Connect Bitbucket once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel.
- 3Ask Notis to create a branch for the repository and target commit in the request, following your branch naming convention.
- 4Choose a Notis webhook trigger and select where run reports should go.
- 5Test with one real request and confirm the branch name is unique and valid.
Questions about this workflow
What details must the request provide?
The repository, target commit hash, and a unique valid branch name or naming information that Notis can use.
Can the branch name include refs/heads/?
No. The action requires a branch name without the refs/heads/ prefix.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Asana to Bitbucket. A trigger fires from one place; an action lands in another.
Asana 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.
Attachment Added to Task
Triggers when an attachment is added to a task.
Create an issue comment
Adds a new comment with markdown support to an existing bitbucket issue.
New Comment on Task
Triggers when a comment is added to a task in a project.
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.
New Task Created
Triggers when a new task is created in a project.
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.
Task Moved to Section
Triggers when a task is moved to a section in a project.
Create snippet comment
Posts a new top-level comment or a threaded reply to an existing comment on a specified bitbucket snippet.
Tag Added to Task
Triggers when a tag is added to a task. Note: Asana's event structure is inverted for tag events — the resource is the task and the parent is the tag. So parent.gid gives the tag GID.
Delete issue
Permanently deletes a specific issue, identified by its `issue id`, from the repository specified by `repo slug` within the given `workspace`.
Task Updated
Triggers when a task is updated in a project.
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.
Asana 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.