Skip to content
Notis

Route changed commitments to the right Jira owner

When a calendar change makes ownership clear, let Notis update the Jira assignee so the next step has an accountable person.

Trigger

Calendar Event Changes

Triggered when a new calendar event occurs (created, updated, or deleted) in the Outlook calendar.

Action

Assign Issue

Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.

Why this helps

Responsibility shifts during scheduling changes, but the Jira ticket remains assigned to someone who is no longer handling the work.

  • Keep ownership aligned with revised commitments.
  • Reduce tickets assigned to someone who is no longer responsible.
  • Make handoffs visible in the team's existing work tracker.

Setup

Build it in a few focused steps.

  • 1Connect Outlook and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, or tell Notis what you want from any channel.
  • 3In one instruction, ask Notis to identify the related issue and change its assignee only when the event clearly names a Jira user as the new owner.
  • 4Choose the Outlook Calendar Event Changes trigger and select where run reports should go.
  • 5Test with one real ownership change and verify the issue assignee.

Questions about this workflow

Can the event name an assignee by email?

Jira assignment supports user lookup. Ask Notis to assign only when the event provides a clear person it can resolve.

What if ownership is not stated?

Instruct Notis to leave ownership unchanged and report that the event did not provide a clear new owner.

Does every calendar change affect Jira ownership?

Your instruction should limit reassignment to events with an explicit change in responsibility and a reliably identified Jira issue.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Outlook to Jira. A trigger fires from one place; an action lands in another.

Outlook triggers

Jira actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Add Attachment

Uploads and attaches a file to a jira issue.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Add Comment

Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.

ActionInstant

New Contact Added

Triggered when a new contact is added in the Outlook contacts.

TriggerInstant

Add Watcher to Issue

Adds a user to an issue's watcher list by account id.

ActionInstant

Calendar Event Changes

Triggered when a new calendar event occurs (created, updated, or deleted) in the Outlook calendar.

TriggerInstant

Assign Issue

Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.

ActionInstant

New Calendar Event

Triggered when a new calendar event is created in the Outlook calendar.

TriggerInstant

Bulk Create Issues

Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.

ActionInstant

New Outlook Message

Triggered when a new message is received in the Outlook mailbox.

TriggerInstant

Create Issue

Creates a new jira issue (e.g., bug, task, story) in a specified project.

ActionInstant

New Sent Message

Triggered when a new message is sent from the Outlook mailbox.

TriggerInstant

Link Issues

Links two jira issues using a specified link type with optional comment.

ActionInstant

Create Project

Creates a new jira project with required lead, template, and type configuration.

ActionInstant

Connect any two apps with Notis in the middle.

Outlook and Jira, or any other combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Jira.