Skip to content
Notis

Move Jira issues forward after a meeting decision

When the team agrees an issue is ready to move, carry that decision into its Jira workflow.

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

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

Teams can agree that work is approved or ready to progress, then leave the issue in an outdated status.

  • Reflect explicit workflow decisions in Jira.
  • Make issue status clearer after a meeting.
  • Reduce the manual step between approval and progress tracking.

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 through any channel.
  • 3Tell Notis to transition an existing Jira issue only when the transcript clearly records an approval or agreed status change.
  • 4Pick Fireflies Transcription Complete as the trigger and choose a report channel.
  • 5Test with a transcript containing an explicit approval for a known Jira issue.

Questions about this workflow

Will it transition issues after a general positive discussion?

Ask Notis to require an explicit approval or agreed workflow change before transitioning an issue.

What if Jira does not allow that transition?

Jira only permits transitions available for the issue's workflow state. Review any failed run report.

Can it also set an assignee during the transition?

The Jira transition action supports user assignment by email. Include that request only when the transcript clearly identifies the owner.

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.