Keep Your Team in Sync: Auto-Post New Issues to Slack
Many neurodivergent teams miss important issues because they require checking multiple apps. This workflow posts every new Jira issue to your Slack channel automatically.
Trigger
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Action
Post message to channel
Deprecated: posts a message to a slack channel, direct message, or private channel. use `send message` instead.
Why this helps
Team members forget to check Jira daily. Important issues get missed or duplicated because no one realized another person was already handling it.
- Ensure all team members see new issues without logging into a separate app
- Reduce duplicate work by surfacing assignments and context immediately
- Keep async teams aligned with real-time visibility into incoming work
Setup
Build it in a few focused steps.
- 1Connect Jira and Slack to Notis via the portal (one-time).
- 2In Notis, create an automation with the prompt: 'When a new issue is created in Jira, post it to the #engineering Slack channel with the title, description, and assignee.'
- 3Select 'New Issue' as the trigger and set your team channel as the report destination.
- 4Test with a sample issue and refine the message format if needed.
- 5Optional: expand to multiple channels (e.g., #marketing, #product) by creating separate automations.
Questions about this workflow
Will this spam our Slack channel?
Only issues created in the Jira project you specify trigger the automation. Filter further in the prompt (e.g., 'only if priority is High or higher').
Can the message include more details like labels or custom fields?
Yes. Notis reads all Jira fields. Ask in your prompt: 'Include the due date and label tags in the Slack message.'
What happens if someone is already discussing this issue in Slack?
Consider a Slack thread-based workflow instead, or use a dedicated #new-issues channel to prevent noise.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Slack. A trigger fires from one place; an action lands in another.
Jira triggers
Slack actions
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Set snooze duration
Deprecated: turns on do not disturb mode for the current user, or changes its duration. use `set dnd duration` instead.
New Project
Triggered when a new project is added in Jira
Add a custom emoji to a Slack team
Deprecated: adds a custom emoji to a slack workspace given a unique name and an image url. use `add emoji` instead.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Add an emoji alias
Adds an alias for an existing custom emoji in a slack enterprise grid organization.
Add a remote file
Adds a reference to an external file (e.g., google drive, dropbox) to slack for discovery and sharing, requiring a unique `external id` and an `external url` accessible by slack.
Add a star to an item
Stars a channel, file, file comment, or a specific message in slack.
Add call participants
Registers new participants added to a slack call.
Add emoji
Adds a custom emoji to a slack workspace given a unique name and an image url; subject to workspace emoji limits.
Add reaction to message
Adds a specified emoji reaction to an existing message in a slack channel, identified by its timestamp; does not remove or retrieve reactions.
Connect any two apps with Notis in the middle.
Not just Jira and Slack. Any combination from 985+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Slack.