Skip to content
Notis

Refresh Jira tickets after signatures complete

Keep Jira aligned with completed agreements without checking every request manually.

Trigger

Recurring schedule

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

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 team can miss completed agreements when Jira tickets do not reflect the latest document status.

  • Catch completed requests during a scheduled review.
  • Update the related Jira issue with the latest status.
  • Spend less time checking status across separate tools.

Setup

Build it in a few focused steps.

  • 1Connect Boloforms and Jira once in Notis.
  • 2Create an automation from any channel or in Automations, then New Automation in the portal.
  • 3Tell Notis to find completed requests not yet reflected in Jira and update their related issues with the status and completion details.
  • 4Choose the recurring schedule and select where run reports should go.
  • 5Test with one completed request and its existing Jira issue.

Questions about this workflow

How often should this run?

Choose a schedule that fits how quickly your team needs to see completion. The schedule is selected in the Notis automation setup.

What does Notis need to match a request to Jira?

Use a Jira key or another stable identifier available in both the request context and issue.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

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

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