Thread Comments Automatically Between Platforms
Every comment finds the right place automatically.
Trigger
Public Team Comment Created
Fires when a new comment is posted on a *public-team* Linear issue. For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_COMMENT_CREATED`.
Action
Create an issue comment
Adds a new comment with markdown support to an existing bitbucket issue.
Why this helps
You add context or questions as comments in Linear, but your developers never see them in Bitbucket. Important discussion stays fragmented across tabs.
- Unified conversation history
- Developers see all context
- No lost comments in tool gaps
Setup
Build it in a few focused steps.
- 1Connect both Linear and Bitbucket integrations to your Notis account
- 2Open the Notis portal and create a new automation
- 3Use this prompt: 'When I comment on a Linear issue, add that comment to the matching Bitbucket issue automatically'
- 4Choose 'Public Team Comment Created' as your trigger event
- 5Set notifications to your preferred channel and test with a practice comment
Questions about this workflow
Do replies sync too?
Yes. All comments and threaded replies sync from Linear to Bitbucket automatically.
Can I disable sync for certain comments?
Yes. Use labels or comment-filtering rules in your automation to control which comments sync.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Bitbucket. A trigger fires from one place; an action lands in another.
Linear 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.
Comment Received Trigger
Triggered when a comment is received.
Create an issue comment
Adds a new comment with markdown support to an existing bitbucket issue.
Issue Created Trigger
Triggered when a new issue is created.
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.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
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.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Create snippet comment
Posts a new top-level comment or a threaded reply to an existing comment on a specified bitbucket snippet.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Delete issue
Permanently deletes a specific issue, identified by its `issue id`, from the repository specified by `repo slug` within the given `workspace`.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
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.
Linear 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.