Turn bug report emails into Bitbucket issues
Keep bug reports from getting buried in your inbox. Ask Notis to turn each useful report into a Bitbucket issue.
Trigger
New Gmail Message Received Trigger
Triggers when a new message is received in Gmail.
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 and can be lost before they reach the engineering backlog.
- Capture reported bugs in the repository backlog
- Reduce manual copying between email and Bitbucket
- Keep the original report available in Gmail
Setup
Build it in a few focused steps.
- 1Connect Gmail and Bitbucket once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, ask Notis to identify bug reports in new messages and create a Bitbucket issue with the useful details.
- 4Pick New Gmail Message Received as the trigger and choose where run reports should go.
- 5Test with one real bug report email.
Questions about this workflow
Does every new email become an issue?
Describe in your instruction which messages count as bug reports. Notis can use the message content to decide whether to create an issue.
What should the automation include in the issue?
Ask Notis to summarize the problem and include relevant reproduction details from the email.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Gmail to Bitbucket. A trigger fires from one place; an action lands in another.
Gmail 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.
Email Sent
Triggers when a Gmail message is sent by the authenticated user. It polls the 'SENT' label and emits metadata including sender, recipients, subject, timestamp, and thread ID.
Create an issue comment
Adds a new comment with markdown support to an existing bitbucket issue.
New Gmail Message Received Trigger
Triggers when a new message is received in Gmail.
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.
Gmail 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.