Skip to content
Notis

Update a Bitbucket issue from a Zendesk ticket

Keep the repository record aligned as customer evidence changes.

Trigger

New Zendesk Ticket

Triggers when a new ticket is created in a specified Zendesk view.

Action

Update an issue

Updates an existing issue in a bitbucket repository by modifying specified attributes; requires `workspace`, `repo slug`, `issue id`, and at least one attribute to update.

Why this helps

Engineering issues become stale when support learns something new after handoff.

  • Keep issue records current
  • Reduce repeated status checks
  • Preserve customer evidence

Setup

Build it in a few focused steps.

  • 1Connect Zendesk and Bitbucket once.
  • 2Create an issue synchronization automation.
  • 3Tell Notis to update the matching Bitbucket issue with the latest Zendesk status, impact, and resolution notes.
  • 4Choose the New Zendesk Ticket trigger and a report channel.
  • 5Test with a ticket linked to an existing issue.

Questions about this workflow

What fields can be updated?

Describe the Bitbucket issue attributes you want changed, such as title, content, priority, or status.

How should matching work?

Specify the shared ticket ID, repository reference, or another reliable identifier.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Zendesk 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 User Created

Triggered when a new user is created in Zendesk.

TriggerInstant

Create an issue comment

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

ActionInstant

New Zendesk Ticket

Triggers when a new ticket is created in a specified Zendesk view.

TriggerPolling

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

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

Create snippet comment

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

ActionInstant

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.

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