Skip to content
Notis

Keep Linear bug issues current with BugHerd feedback

When a report changes, carry the useful new details into the issue your team already tracks.

Trigger

Webhook received

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

Action

Update issue

Updates an existing linear issue using its `issue id`; requires at least one other attribute for modification, and all provided entity ids (for state, assignee, labels, etc.) must be valid.

Why this helps

New report details can remain disconnected from an existing issue, leaving the team with stale context.

  • Add meaningful new report details to an existing issue.
  • Reduce duplicate issues caused by overlooked updates.
  • Keep the issue description aligned with available source context.

Setup

Build it in a few focused steps.

  • 1Connect BugHerd and Linear once in the Notis portal.
  • 2Create an automation in Automations, New Automation, or tell Notis in plain language from any channel.
  • 3Describe the outcome in one instruction: when a BugHerd report provides new information for a known Linear issue, update that issue with the relevant details.
  • 4Choose the webhook trigger and select where run reports should go.
  • 5Test with one real report that can be matched to an existing Linear issue.

Questions about this workflow

What does Notis need to match a report to an existing issue?

The report must include a reliable identifier or other matching information, or you must provide a matching rule. Notis cannot invent missing issue history.

Will this create a new issue if no match is found?

This workflow is for updating known issues. State in the instruction how Notis should handle an uncertain match, such as leaving it for review instead of updating the wrong issue.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Bugherd triggers

Linear actions

Recurring trigger

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

TriggerScheduled

Create linear attachment

Creates a new attachment and associates it with a specific, existing linear issue.

ActionInstant

Webhook trigger

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

TriggerInstant

Create a comment

Creates a new comment on a specified linear issue.

ActionInstant

Create linear issue

Creates a new issue in a specified linear project and team, requiring a title and description, and allowing for optional properties like assignee, state, priority, cycle, and due date.

ActionInstant

Get create issue default params

Fetches a linear team's default issue estimate and state, useful for pre-filling new issue forms.

ActionInstant

Create a label

Creates a new label in linear for a specified team, used to categorize and organize issues.

ActionInstant

Delete issue

Archives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.

ActionInstant

Get all teams

Retrieves all teams from the linear workspace without requiring any parameters.

ActionInstant

Download issue attachments

Downloads a specific attachment from a linear issue; the `file name` must include the correct file extension.

ActionInstant

Connect any two apps with Notis in the middle.

Bugherd and Linear, 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 Linear.