Keep Linear work aligned with Bugbug test case changes
When a test case changes, the related Linear work may need a matching update. Send the change details to Notis and keep the issue aligned with what was actually changed.
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
Test maintenance and engineering follow-up can drift apart when updates are recorded in separate tools.
- Keep issue context aligned with a supplied test case change.
- Reduce manual status and description updates across tools.
- Preserve a clear record of why follow-up changed.
Setup
Build it in a few focused steps.
- 1Connect Bugbug and Linear once in the Notis portal.
- 2Create an automation in Automations, or tell Notis from any channel to create one.
- 3Ask Notis in one instruction to update the supplied Linear issue with the Bugbug test case change details.
- 4Choose notis_webhook as the trigger and select where run reports should go.
- 5Test with one real test case update and its related Linear issue.
Questions about this workflow
What issue fields can be changed?
The Linear update action requires an issue ID and at least one valid attribute to modify. Specify the intended update and supply the required values.
Can Notis identify the related issue automatically?
Provide its identifier in the request or include clear context that allows Notis to identify it. It should not guess when the relationship is unclear.
Does this read a complete test case history?
Only details made available through the webhook or connected access can be used. Include any needed before-and-after context in the request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bugbug to Linear. A trigger fires from one place; an action lands in another.
Bugbug triggers
Linear actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create linear attachment
Creates a new attachment and associates it with a specific, existing linear issue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create a comment
Creates a new comment on a specified linear issue.
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.
Get create issue default params
Fetches a linear team's default issue estimate and state, useful for pre-filling new issue forms.
Create a label
Creates a new label in linear for a specified team, used to categorize and organize issues.
Delete issue
Archives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.
Get all teams
Retrieves all teams from the linear workspace without requiring any parameters.
Download issue attachments
Downloads a specific attachment from a linear issue; the `file name` must include the correct file extension.
Connect any two apps with Notis in the middle.
Bugbug 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.