Keep Jira scope changes connected to their reason
Record what changed in the scope and why, right beside the Jira issue affected by the decision.
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
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
Why this helps
Scope changes made verbally can be difficult to reconstruct later, especially when the ticket does not explain the decision.
- Keep the reason for scope changes with the affected work.
- Help teammates understand later revisions.
- Reduce confusion when plans shift after a discussion.
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 tell Notis in any channel.
- 3Ask Notis to comment on an identifiable Jira issue only when the transcript explicitly changes its scope, summarizing what changed and why.
- 4Choose Fireflies Transcription Complete as the trigger and select a destination for run reports.
- 5Test with a transcript containing a clear scope decision for a known issue.
Questions about this workflow
Will it comment on every proposed scope change?
Tell Notis to comment only on decisions the team explicitly agreed to, not proposals or open questions.
What if the reason is not discussed?
Ask Notis to summarize only what the transcript provides and avoid inventing a rationale.
Can it also update the issue description?
This workflow adds a comment to preserve the decision. Updating issue fields would use a separate Jira edit action.
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.
Add Attachment
Uploads and attaches a file to a jira issue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
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.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
Link Issues
Links two jira issues using a specified link type with optional comment.
Create Project
Creates a new jira project with required lead, template, and type configuration.
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.