Skip to content
Notis

Update Jira issues when document details change

When a newer extraction arrives, keep the related Jira ticket in step with the latest supplied details.

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

Teams may keep working from stale ticket details after a document has been corrected or processed again.

  • Keep an existing ticket aligned with a newer extraction payload.
  • Highlight changed or uncertain details for human review.
  • Reduce manual copying of corrected document information.

Setup

Build it in a few focused steps.

  • 1Connect Affinda and Jira once in the Notis portal.
  • 2Create an automation in the portal under Automations, New Automation, or tell Notis in plain language from any channel.
  • 3Describe that an incoming updated extraction should revise the referenced Jira issue with supplied current details and summarize what changed.
  • 4Pick the webhook trigger and choose where run reports should go.
  • 5Test with one real updated extraction and its Jira issue key.

Questions about this workflow

What does the request need to identify?

Include the Jira issue key or another unambiguous issue reference, along with the updated extraction details.

Can Notis determine which values changed?

It can compare values only when the new payload and a previous baseline are available. Include prior values if you want a comparison.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

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

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