Update Jira scope from Slack clarifications
Keep Jira descriptions aligned when a Slack conversation changes what a task includes.
Trigger
Channel Message Received
Triggered when a message is posted in a Slack channel (public, private, or multi-party IM). Does NOT match direct messages.
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
Scope clarifications can stay in chat while the Jira issue continues to describe outdated work.
- Keep issue descriptions closer to current decisions.
- Reduce manual follow-up after a scope change.
- Help teammates returning to a ticket see updated context.
Setup
Build it in a few focused steps.
- 1Connect Slackbot and Jira once in the Notis portal.
- 2Create an automation for scope updates.
- 3Tell Notis to update the description of a Jira issue only when a channel message clearly changes its scope, retaining existing useful context and noting the clarification.
- 4Choose Channel Message Received as the trigger.
- 5Choose a report channel and test with a real scope clarification and issue key.
Questions about this workflow
Will every suggestion in Slack change a Jira issue?
Instruct Notis to act only on clear scope changes, and test with examples of both decisions and tentative discussion.
Can the existing issue description be retained?
Ask Notis to preserve useful existing context while incorporating the clarification, then review the test result.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Slackbot to Jira. A trigger fires from one place; an action lands in another.
Slackbot 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.
New Channel Created Trigger
Triggered when a new channel is created in Slack.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
Channel Message Received
Triggered when a message is posted in a Slack channel (public, private, or multi-party IM). Does NOT match direct messages.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Direct Message Received
Triggered when a new direct message (DM) is sent to a user in Slack. Catches all DMs across all DM channels.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Message Reaction Added
Triggered when a reaction is added to a message in Slack. Supports optional filtering by channel and emoji name.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
Message Reaction Removed
Triggered when a reaction is removed from a message in Slack. Supports optional filtering by channel and emoji name.
Link Issues
Links two jira issues using a specified link type with optional comment.
Reaction Added Trigger
DEPRECATED: use `SLACK_MESSAGE_REACTION_ADDED` instead. Triggered when a reaction is added to a message in Slack.
Create Project
Creates a new jira project with required lead, template, and type configuration.
Connect any two apps with Notis in the middle.
Slackbot 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.