Skip to content
Notis

Move approved Jira work forward from email

When a stakeholder approves work by email, let Notis transition the identified Jira issue to the next appropriate workflow state.

Trigger

New Outlook Message

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

Action

Transition Issue

Transitions a jira issue to a different workflow state, with support for transition name lookup and user assignment by email.

Why this helps

An approval arrives by email, but the ticket remains in its old state until someone notices and updates it manually.

  • Reduce delay between approval and the next workflow step.
  • Keep Jira status aligned with clear stakeholder decisions.
  • Avoid a manual context switch for routine approvals.

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, specify what approval language qualifies, how to identify the Jira issue, and which available transition should follow.
  • 4Choose the Outlook New Outlook Message trigger and select where run reports should go.
  • 5Test with one real approval email and confirm the issue reaches the intended state.

Questions about this workflow

Can Notis choose a transition that is not available on the issue?

No. Jira provides the available transitions for the issue. Instruct Notis to use the appropriate available transition and report if none matches.

Will a vague positive reply trigger a transition?

Define what counts as an explicit approval and ask Notis to leave the issue unchanged when the message is ambiguous.

How does Notis locate the issue?

Include a Jira key in the email or specify another reliable issue identifier that Notis can use.

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.