Keep Jira scope aligned with incoming email
When a new message clarifies the work, have Notis update the identified Jira issue so the ticket reflects the latest request.
Trigger
New Outlook Message
Triggered when a new message is received in the Outlook mailbox.
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 customer or teammate clarifies requirements by email, but the Jira issue continues to describe the earlier scope.
- Keep requirements current in the active issue.
- Reduce mismatches between stakeholder email and Jira.
- Preserve the meaning of a scope change for the team.
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 update an existing issue when a new message clearly changes or clarifies its scope.
- 4Choose the Outlook New Outlook Message trigger and select where run reports should go.
- 5Test with one real scope clarification that identifies an issue and review the update.
Questions about this workflow
Will this create a new issue when no match exists?
This workflow updates an existing Jira issue. Tell Notis to report a missing or uncertain match for review.
Can Notis distinguish a clarification from a new request?
Describe what constitutes a scope change and how to handle a separate request. Notis will use the message content and your instruction.
How should the email identify the existing issue?
A Jira key in the message is a reliable identifier. You can specify another clear reference that appears in the email.
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.