Categorize Legacy Code Errors Automatically
Update a legacy issue in Linear and Notis creates a custom Bugsnag field to track which errors stem from old code, keeping regressions separate from new bugs.
Trigger
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Action
Create Custom Event Field
Tool to create a custom event field for a project. use after confirming the project id to add a new filterable field. example: "create a field 'user.id' mapping to 'metadata.user.id' for project 515fb..."
Why this helps
You manage legacy code issues in Linear but can't easily identify legacy-related errors in Bugsnag. New bugs and old-code problems get mixed together.
- Automatically track legacy code-related errors separately
- Reduce confusion between new bugs and technical debt issues
- Enable targeted legacy code error analysis and prioritization
- Maintain clear error categorization across teams
Setup
Build it in a few focused steps.
- 1Connect Linear and Bugsnag to Notis.
- 2Create automation: 'When a private team issue is updated with legacy label, create a custom field in Bugsnag to tag legacy errors.'
- 3Select 'Private Team Issue Properties Updated' as the trigger and your notification channel.
- 4Test by updating a private team legacy issue and verify the custom field is created.
Questions about this workflow
How do I distinguish legacy errors from new ones?
The custom field lets you filter and segment errors by code version or legacy status. Notis tags relevant errors automatically.
Can I migrate legacy categorization later?
Yes. You can update the field definition and re-tag errors as your codebase evolves.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Bugsnag. A trigger fires from one place; an action lands in another.
Linear triggers
Bugsnag actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Bulk Update Errors
Tool to bulk update multiple errors in a project. use when batching identical updates across many errors.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Configure Integration
Tool to configure a new integration for a bugsnag project. use after selecting integration key and preparing credentials.
Comment Received Trigger
Triggered when a comment is received.
Invite Collaborator
Tool to invite a collaborator to an organization. use when you need to add a new user by email to grant them access. ensure the organization id is correct before calling.
Issue Created Trigger
Triggered when a new issue is created.
Create Custom Event Field
Tool to create a custom event field for a project. use after confirming the project id to add a new filterable field. example: "create a field 'user.id' mapping to 'metadata.user.id' for project 515fb..."
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Create Saved Search
Tool to create a new saved search for a project. use when you need to persist a set of filters and sort order as a saved search for a project after confirming project details.
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).
Delete All Errors in a Project
Tool to delete all errors in a project. use when you need to remove all error and event data for a given project. use with caution after confirming the project id, as this action is irreversible and requires project owner or organization administrator permissions.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Delete Collaborator
Tool to remove a collaborator from an organization. use when revoking collaborator access after confirming both organization and collaborator ids. requires organization administrator privileges.
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 a configured integration
Tool to delete a configured integration. use when you need to remove an existing integration from a project after confirming the integration id. this action cannot be undone and requires organization administrator or project owner permissions.
Connect any two apps with Notis in the middle.
Linear and Bugsnag, 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 Bugsnag.