Keep release follow-ups attached to their Bitbucket issue
Release notes and follow-up reports often arrive after the original ticket is closed from view. Keep new context on the issue it belongs to.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create an issue comment
Adds a new comment with markdown support to an existing bitbucket issue.
Why this helps
Important release feedback gets scattered across Ably conversations instead of staying with the engineering issue it informs.
- Keep post-release observations with the related issue.
- Preserve new context without creating a duplicate ticket.
- Make follow-up easier to find during later review.
Setup
Build it in a few focused steps.
- 1Connect Ably and Bitbucket once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for release follow-ups.
- 3Describe that each incoming release follow-up should be added as a comment to its referenced Bitbucket issue.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real follow-up and verify the comment is on the intended issue.
Questions about this workflow
What information must the webhook include?
Include enough information to identify the workspace, repository, issue, and the follow-up text.
Does this create a new issue?
No. It adds a comment to an existing issue identified by the incoming request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ably to Bitbucket. A trigger fires from one place; an action lands in another.
Ably 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.
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.
Ably 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.