Keep Jira delivery details current when dates shift
When an event tied to a delivery commitment changes, let Notis update the corresponding Jira issue with the revised schedule.
Trigger
Calendar Event Changes
Triggered when a new calendar event occurs (created, updated, or deleted) in the Outlook calendar.
Action
Edit Issue
Updates an existing jira issue with field values and operations. supports direct field parameters (summary, description, assignee, priority, etc.) that are merged with the fields parameter. direct parameters take precedence.
Why this helps
A delivery date changes in the calendar, but Jira still shows the old commitment and creates avoidable confusion for the team.
- Make revised commitments visible in Jira.
- Reduce conflicting dates across calendar and backlog.
- Keep a clear explanation of why the schedule changed.
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, describe how to identify the delivery issue and update its schedule context when the calendar event changes.
- 4Choose the Outlook Calendar Event Changes trigger and select where run reports should go.
- 5Test with one real date change and review the Jira issue.
Questions about this workflow
Can the action change a Jira due date field?
The Edit Issue action supports field updates. Tell Notis to update a date only when the event provides a clear replacement date and the issue is identified.
What if a change is only a new meeting time?
Clarify in your instruction which event changes affect a delivery commitment and which are routine calendar adjustments.
How can I make sure the right issue is updated?
Include a Jira key or another reliable issue identifier in the event details and instruct Notis how to use it.
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.
Add Attachment
Uploads and attaches a file to a jira issue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
New Contact Added
Triggered when a new contact is added in the Outlook contacts.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
Calendar Event Changes
Triggered when a new calendar event occurs (created, updated, or deleted) in the Outlook calendar.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
New Calendar Event
Triggered when a new calendar event is created in the Outlook calendar.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
New Outlook Message
Triggered when a new message is received in the Outlook mailbox.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
New Sent Message
Triggered when a new message is sent from the Outlook mailbox.
Link Issues
Links two jira issues using a specified link type with optional comment.
Create Project
Creates a new jira project with required lead, template, and type configuration.
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.