Align issue priority policy and incident severity
Keep incident classification options aligned with how the team now describes urgency, without maintaining separate lists by hand.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Create Severity
Tool to create a new severity level in incident.io. Use when you need to define a new severity classification for incidents with a specific rank and description.
Why this helps
Priority vocabulary evolves in Linear, while incident.io lacks a matching severity option for the response team.
- Keeps priority and severity language easier to reconcile.
- Reduces configuration follow-up when policy changes.
- Helps responders classify incidents consistently.
Setup
Build it in a few focused steps.
- 1Connect Linear and incident.io to Notis once in the portal.
- 2Ask Notis to create a new incident.io severity only when a Linear priority change signals a genuinely new classification is needed.
- 3Select the Linear Issue Updated trigger and choose a channel for run reports.
- 4Test with a planned priority policy example and verify that a duplicate severity is not created.
Questions about this workflow
Should every priority update create a severity?
No. Use this only when the change represents a new classification that incident.io does not already have.
Why include a duplicate check in the instruction?
Severity options are configuration, so a repeat event should not create redundant choices.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to incident.io. A trigger fires from one place; an action lands in another.
Linear triggers
incident.io actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Alert Attribute V2
Tool to create an alert attribute in incident.io. Use when you need to define structured data fields that can be parsed from alerts coming in via alert sources. Alert attributes allow you to extract and organize information from incoming alerts.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Alert Route V2
Tool to create an alert route in incident.io. Use when you need to configure how alerts should be processed, routed, and potentially converted into incidents based on conditions, grouping rules, and templates.
Comment Received Trigger
Triggered when a comment is received.
Create Alert Source V2
Tool to create a new alert source in incident.io. Use when you need to set up a new integration for receiving alerts from external systems via HTTP webhooks or manual entry.
Issue Created Trigger
Triggered when a new issue is created.
Create Catalog Entry V2
Tool to create a catalog entry in incident.io. Use when you need to add a new entry to a catalog type with specific attribute values. Catalog entries represent items like teams, services, or custom resources in your incident management workflow.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Create Catalog Entry V3
Tool to create a catalog entry in incident.io using the V3 API. Use when you need to add a new entry to a catalog type with specific attribute values. Catalog entries represent items like teams, services, or custom resources in your incident management workflow.
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 Catalog Type V3
Tool to create a new catalog type in incident.io V3 API. Use when you need to define custom resource types for your organization's catalog, such as teams, services, or infrastructure components.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Create Custom Field Option
Tool to create a new custom field option in incident.io. Use when you need to add a new selectable value to an existing custom field.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Create Custom Field V2
Tool to create a custom field in incident.io using the V2 API. Use when you need to add a new custom field to track additional information during incidents.
Connect any two apps with Notis in the middle.
Linear and incident.io, 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 incident.io.