Skip to content
Notis

Add email context to Bitbucket issues

Keep engineering context in the issue where work happens.

Trigger

New Outlook Message

Triggered when a new message is received in the Outlook mailbox.

Action

Create an issue comment

Adds a new comment with markdown support to an existing bitbucket issue.

Why this helps

Decisions and clarifications stay trapped in email threads after an issue is opened.

  • Preserve decisions beside implementation work
  • Reduce repeated explanations
  • Make issue history easier to scan

Setup

Build it in a few focused steps.

  • 1Connect Outlook and Bitbucket once in Notis.
  • 2Create an automation named Email context to issue comment.
  • 3Tell Notis to identify the matching issue and add only new decisions, requirements, or clarifications as a markdown comment.
  • 4Pick New Outlook Message as the trigger and choose a report channel.
  • 5Test with a real clarification email.

Questions about this workflow

How does Notis identify the issue?

It can use issue keys, repository names, or other references present in the email and ask for review when ambiguous.

Will it copy the whole thread?

You can instruct Notis to summarize relevant context instead of copying unrelated text.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Outlook to Bitbucket. A trigger fires from one place; an action lands in another.

Outlook triggers

Bitbucket actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

New Contact Added

Triggered when a new contact is added in the Outlook contacts.

TriggerInstant

Create an issue comment

Adds a new comment with markdown support to an existing bitbucket issue.

ActionInstant

Calendar Event Changes

Triggered when a new calendar event occurs (created, updated, or deleted) in the Outlook calendar.

TriggerInstant

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.

ActionInstant

New Calendar Event

Triggered when a new calendar event is created in the Outlook calendar.

TriggerInstant

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.

ActionInstant

New Outlook Message

Triggered when a new message is received in the Outlook mailbox.

TriggerInstant

Create snippet comment

Posts a new top-level comment or a threaded reply to an existing comment on a specified bitbucket snippet.

ActionInstant

New Sent Message

Triggered when a new message is sent from the Outlook mailbox.

TriggerInstant

Delete issue

Permanently deletes a specific issue, identified by its `issue id`, from the repository specified by `repo slug` within the given `workspace`.

ActionInstant

Delete repository

Permanently deletes a specified bitbucket repository; this action is irreversible and does not affect forks.

ActionInstant

Connect any two apps with Notis in the middle.

Outlook 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.