Keep Linear ownership in step with Jira
When a Jira issue changes hands, the Linear copy still names the old owner, and suddenly two people think it is not theirs. Notis updates the Linear issue on reassignment, so accountability stays crystal clear.
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
Mismatched ownership between Jira and Linear is how work ends up assigned to nobody, with each person assuming the other has it.
- Ownership changes in Jira reach Linear so the right person is always named.
- You avoid the dropped-ball trap of work that belongs to nobody.
- Accountability stays consistent without you policing two tools.
Setup
Build it in a few focused steps.
- 1Connect Jira and Linear to Notis once from the portal.
- 2Open your portal link from Notis and start a New Automation, or ask Notis in plain language.
- 3Write one instruction, for example: When a Jira issue is reassigned, update the matching Linear issue to the new owner.
- 4Select the Jira Updated Issue event as the trigger.
- 5Choose a report channel and test by reassigning one real Jira issue.
Questions about this workflow
What if the person is not in Linear?
Notis reports the run to your channel so you can catch mismatches. You can tell it how to handle unknown owners in your instruction.
Does it also carry other changes?
This automation focuses on ownership because that is what your instruction describes. Add other automations for status or details.
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.