Skip to content
Notis

Keep Jira priorities in step with team decisions

When the team agrees that work needs a different level of attention, carry that decision into Jira.

Trigger

Transcription Complete Trigger

Triggers when a transcription is complete. Polls Fireflies API for transcripts created or updated since the last poll time. Handles rate limiting gracefully.

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

Priorities discussed in a meeting can be forgotten, leaving the team to make decisions from an outdated queue.

  • Reflect explicit reprioritization decisions in the issue.
  • Keep the Jira queue closer to the team's current focus.
  • Avoid changing priority based on casual or ambiguous comments.

Setup

Build it in a few focused steps.

  • 1Connect Fireflies and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, or ask Notis from any channel.
  • 3In one instruction, ask Notis to change an issue's priority only when the transcript records a clear reprioritization decision.
  • 4Select Fireflies Transcription Complete as the trigger and where run reports should go.
  • 5Test with a meeting transcript that explicitly reprioritizes a known Jira issue.

Questions about this workflow

Will it infer priority from words like 'important'?

Ask Notis to require an explicit decision to change the issue's priority.

What if the new priority is not stated?

The workflow should skip the change unless the transcript clearly identifies the intended priority.

Does this change the issue status?

No. It updates issue details such as priority, while a workflow status change uses a Jira transition.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Fireflies 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

Transcription Complete Trigger

Triggers when a transcription is complete. Polls Fireflies API for transcripts created or updated since the last poll time. Handles rate limiting gracefully.

TriggerPolling

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.

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