Skip to content
Notis

Keep Jira tickets current after follow-up meetings

Send Notis the meeting update and ticket key. It can revise the existing issue to reflect the latest agreement.

Trigger

Webhook received

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

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 changed deadline, scope, or priority in a meeting can leave the Jira ticket out of date.

  • Reflect new agreements in the ticket
  • Keep changes tied to meeting context
  • Avoid relying on someone to remember a manual update

Setup

Build it in a few focused steps.

  • 1Connect Avoma and Jira once in the Notis portal.
  • 2Create an automation from any channel or in Automations, New Automation.
  • 3Tell Notis to update the specified Jira issue only when the submitted Avoma recap states a changed commitment, and describe which changes matter.
  • 4Choose the webhook trigger and select where run reports should go.
  • 5Test with one real follow-up recap and its existing Jira issue key.

Questions about this workflow

What information can this workflow update?

In your instruction, specify the relevant issue fields and the kinds of changes in the submitted recap that should update them.

Does it infer a new deadline if none is stated?

No. Ask Notis to use only changes stated in the meeting information you provide.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Avoma 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

Add Watcher to Issue

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

ActionInstant

Assign Issue

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

ActionInstant

Bulk Create Issues

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

ActionInstant

Create Issue

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

ActionInstant

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.

Avoma 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.