Announce Jira status changes as Linear comments
Not every Jira change deserves a whole ticket rewrite, but your team still needs to know. Notis posts a short comment on the linked Linear issue whenever the Jira status moves, so context lands where the work happens.
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
Create a comment
Creates a new comment on a specified linear issue.
Why this helps
Chasing down whether a Jira ticket moved forward means opening yet another tab, and that context-switch is the tax that breaks your focus.
- Your builders learn about Jira movement inside Linear, with no extra tab.
- Updates arrive as lightweight comments instead of noisy ticket rewrites.
- You stop being the messenger who relays status by hand.
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 to Notis directly from any channel.
- 3Give one plain-language instruction, for example: When a Jira issue's status changes, add a comment to the linked Linear issue noting the new status.
- 4Choose the Jira Updated Issue trigger.
- 5Set the channel for run confirmations and test with one real status change in Jira.
Questions about this workflow
Will it comment on every tiny Jira edit?
You decide in your instruction. Tell Notis to comment only on status changes and it will focus on those.
Do I write the comment text?
You describe what the comment should say in plain language. Notis composes it for each run, so there is nothing to template manually.
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.