Preserve issue relationships across tools
Mark issues as related in Linear—Jira links them automatically. Dependencies stay visible everywhere.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Link Issues
Links two jira issues using a specified link type with optional comment.
Why this helps
You mark issues as related in Linear, but Jira has no clue they're connected. Teams can't see the dependency graph and plan work incorrectly.
- Dependency graph stays current across both systems
- Teams see which issues block which—no surprises
- Better planning and parallel work without conflicts
- Reduces 'oh, we should have coordinated this' delays
Setup
Build it in a few focused steps.
- 1Connect Linear and Jira to Notis
- 2Set up automation: 'When a Linear issue is marked as related or blocked by another issue, automatically link the corresponding Jira issues with the same relationship type.'
- 3Choose your notification channel
- 4Link two test Linear issues and verify Jira links appear
Questions about this workflow
What if the relationship type differs between Linear and Jira?
Notis maps common types (blocks/blocked-by, relates-to, depends-on). Custom mappings can be added to your prompt.
Does this work for issues that don't have direct Jira counterparts?
No. Notis only links issues that already exist in both systems. If a related issue isn't in Jira, Notis will notify you.
Can I remove links if a Linear relationship is removed?
Yes. Add to your prompt: 'if a relationship is removed in Linear, also remove the Jira link'.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Jira. A trigger fires from one place; an action lands in another.
Linear triggers
Jira actions
Comment Received Trigger
Triggered when a comment is received.
Add Attachment
Uploads and attaches a file to a jira issue.
Issue Created Trigger
Triggered when a new issue is created.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
Project Created
Fires when a new Linear project is created. Covers projects in both public and private teams — polls with the connected user's token, so visibility matches what the connected user can see in Linear.
Link Issues
Links two jira issues using a specified link type with optional comment.
Project Properties Updated
Fires when properties on a Linear project change (status, lead, target date, priority, etc.). Covers projects in both public and private teams — polls with the connected user's token.
Create Project
Creates a new jira project with required lead, template, and type configuration.
Connect any two apps with Notis in the middle.
Not just Linear and Jira. 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 Jira.