Skip to content
Notis

Close the loop on Jira work from Bolna calls

When a conversation confirms that tracked work is done, move the Jira issue forward without leaving it in an outdated state.

Trigger

Webhook received

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

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

Completed work can remain open in Jira when a call confirms the result but nobody returns to update the ticket.

  • Update issue workflow state when completion is clearly confirmed.
  • Keep Jira status closer to the outcome discussed on the call.
  • Avoid treating a tentative update as confirmed completion.

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 transition the Jira issue identified in the Bolna event only when the conversation clearly confirms completion, using the appropriate available Jira transition.
  • 4Choose the webhook trigger and select where run reports should go.
  • 5Test with one real example where the issue is identified and completion is explicit.

Questions about this workflow

Does this close every issue mentioned in a call?

No. The instruction should require clear confirmation that the tracked work is complete.

What if Jira has no matching transition?

The action can use an available workflow transition. Ensure the intended transition exists for the issue's current state.

Can Notis distinguish a plan from completion?

Ask it to require an explicit confirmation of completed work and to leave the issue unchanged when the conversation is tentative.

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.