Turn emailed bug reports into Bitbucket issues
Keep bug reports moving without copying details between your inbox and Bitbucket.
Trigger
New Email Received
Trigger for new emails in an AgentMail inbox
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
Bug reports arrive by email, then lose key context while someone rewrites them as issues.
- Create an issue while the report is still easy to review.
- Summarize the problem and include relevant email details.
- Reduce manual copying between inbox and repository.
Setup
Build it in a few focused steps.
- 1Connect Agent Mail and Bitbucket once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to turn each incoming bug report into a concise Bitbucket issue with the email context and reproduction steps.
- 4Choose New Email Received as the trigger and select where run reports should go.
- 5Test with one real bug report email.
Questions about this workflow
Can Notis tell a bug report from other email?
Describe the criteria in your instruction. Notis can use the incoming email content, but it cannot rely on labels or history that Agent Mail does not provide.
Will the issue include the original report?
Ask Notis to include the useful details or a concise summary from the email in the issue it creates.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Agent mail to Bitbucket. A trigger fires from one place; an action lands in another.
Agent mail 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 Email Received
Trigger for new emails in an AgentMail inbox
Create an issue comment
Adds a new comment with markdown support to an existing bitbucket issue.
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.
Agent mail 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.