Push Jira issue updates into Linear as they happen
Edit an issue in Jira and the matching Linear issue drifts out of date. Notis catches the change and updates the Linear copy, so you are not the human sync between two trackers.
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
Updating the same ticket in two places is exactly the kind of repetitive housekeeping that gets skipped, and then the two tools quietly disagree.
- A status or detail change in Jira reaches Linear without a second edit from you.
- Both trackers stay trustworthy, so nobody works off a stale ticket.
- You drop the low-value habit of updating the same thing twice.
Setup
Build it in a few focused steps.
- 1Connect Jira and Linear to Notis once through the portal.
- 2Open your portal link from Notis and start a New Automation, or simply ask Notis in plain language.
- 3Write the instruction as one sentence, for example: When a Jira issue is updated, update the matching Linear issue to reflect the change.
- 4Select the Jira Updated Issue event as the trigger.
- 5Pick a channel for run reports and test it by editing one real Jira issue.
Questions about this workflow
Does this fire when someone comments on a Jira issue?
No. The Jira Updated Issue trigger reacts to field changes like status or assignee, not to comment activity.
How does Notis know which Linear issue to update?
Notis matches on the details in your instruction. You describe the intent once and it handles the lookup, with no manual mapping.
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 985+ 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.