Skip to content
Notis

Update Jira issue details from Bolna calls

Carry a meaningful change from a voice conversation into the existing Jira issue, with less manual context switching.

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

Ticket details can become stale when new information from a conversation has to be copied into Jira by hand.

  • Keep an existing Jira issue aligned with new conversation details.
  • Update only when the call provides a clear change.
  • Reduce manual copying between voice and issue tracking.

Setup

Build it in a few focused steps.

  • 1Connect Bolna and Jira once in the Notis portal.
  • 2Create an automation from any channel or in Automations, New Automation.
  • 3Tell Notis to update the existing Jira issue identified by the Bolna event only when the conversation provides a clear, supported change, and to preserve unrelated details.
  • 4Choose the webhook trigger and select where run reports should go.
  • 5Test with one real example that includes an issue reference and a concrete change.

Questions about this workflow

What can Notis update?

It can update issue details supported by the Jira action and grounded in the conversation. State which changes you want in the automation instruction.

What if the conversation has no clear change?

The instruction can tell Notis to leave the issue untouched when the call does not provide a clear update.

Does this work without an issue reference?

No. The event must identify the existing Jira issue to update.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

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

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