Close the loop in Linear when Jira work finishes
A finished Jira ticket that still sits open in Linear is a false to-do. Notis archives the Linear copy when the Jira issue is marked done, so your board reflects reality instead of ghosts.
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
Delete issue
Archives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.
Why this helps
Stale, already-finished issues clutter your Linear board and make it hard to trust what is actually left to do.
- Finished work leaves your Linear board on its own, so the board stays trustworthy.
- You avoid the double-close chore of marking the same thing done twice.
- What remains in Linear is genuinely what is left, which lowers the noise you have to sift.
Setup
Build it in a few focused steps.
- 1Connect Jira and Linear to Notis once from the portal.
- 2Open the portal link Notis sends you and start a New Automation, or just tell Notis what you want.
- 3Describe it in one sentence, for example: When a Jira issue is marked done, archive the matching Linear issue.
- 4Pick the Jira Updated Issue event as the trigger.
- 5Choose a report channel and test by closing one real Jira issue.
Questions about this workflow
Is archiving the same as deleting in Linear?
Archiving is Linear's standard way to remove an issue from active view, and the action is idempotent, so re-running it causes no harm.
Can I limit it to a specific done status?
Yes. Name the status you mean in your plain-language instruction and Notis will act only on that transition.
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.