Keep Linear priorities aligned with Jira
When priorities shift in Jira but not in Linear, your team keeps building against yesterday's plan. Notis updates the Linear issue when the Jira priority changes, so the order of work reflects what actually matters now.
Trigger
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
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
A priority change that lives only in Jira means engineering keeps working the old order, and the urgent thing waits behind the routine one.
- Priority shifts in Jira reach Linear so the build order stays current.
- The urgent work rises in Linear without you nudging the team.
- Engineering trusts the Linear order because it mirrors the latest call.
Setup
Build it in a few focused steps.
- 1Connect Jira and Linear to Notis one time in the portal.
- 2Ask Notis for your portal link and create a New Automation, or describe it conversationally.
- 3Write one instruction, for example: When a Jira issue's priority changes, update the matching Linear issue to the new priority.
- 4Select the Jira Updated Issue event as the trigger.
- 5Pick a report channel and test by changing one real Jira issue's priority.
Questions about this workflow
Does it react to any Jira edit?
It focuses on priority because that is what your instruction targets. The Updated Issue trigger fires on field changes, and Notis acts on the priority.
Will engineering be notified?
Notis reports each run to your chosen channel, and the update itself is visible in Linear.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Linear. A trigger fires from one place; an action lands in another.
Jira triggers
Linear actions
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Create linear attachment
Creates a new attachment and associates it with a specific, existing linear issue.
New Project
Triggered when a new project is added in Jira
Create a comment
Creates a new comment on a specified linear issue.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
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.
Not just Jira and Linear. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Linear.