Turn engineering intake requests into Bitbucket issues
Send one request and give incoming work a trackable issue in the right repository.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
Engineering requests arrive through different channels and can be lost before anyone turns them into actionable issues.
- Create a consistent destination for incoming work.
- Keep request details with the engineering issue.
- Reduce manual copying from intake forms or internal tools.
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 an issue from the request details, using the specified workspace and repository.
- 4Choose a Notis webhook trigger and select where run reports should go.
- 5Test with one real intake request and verify the issue details and repository.
Questions about this workflow
Can this set an assignee?
Yes, if you ask Notis to assign the issue and the chosen person has repository access.
Can it set a milestone or component?
Those values can be included when creating an issue if their ids exist in the repository.
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.