Skip to content
Notis

Refresh linked Jira tickets before meetings

Give meeting-linked Jira issues a scheduled check so attendees and timing reflect the latest available event details.

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 ticket linked to a meeting can keep showing old timing or attendee details after the calendar entry changes.

  • Update meeting context before the event begins.
  • Reduce stale attendee and timing details in Jira.
  • Keep meeting-linked work easier to act on.

Setup

Build it in a few focused steps.

  • 1Connect Calendarhero and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a name.
  • 3Tell Notis to find upcoming events linked to Jira issue keys and refresh those issues with current event details.
  • 4Pick a recurring schedule and choose where run reports should go.
  • 5Test it with one real event linked to a Jira issue.

Questions about this workflow

How are meetings linked to Jira issues?

Provide the issue key in the event details or an identifying reference that Notis can use to locate the related issue.

Which ticket details are updated?

Describe the meeting details you want refreshed in the automation instruction. Notis can only update information available from Calendarhero and supported by the Jira action.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

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

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