Skip to content

Connect Jira to Slack

Jira tracks the work, but Slack is where teams notice problems and ask for help. Connecting them turns Slack requests and alerts into proper tickets, and brings Jira progress, stale tickets and releases back into the channels people read every day.

Ideas

What you can do with Jira and Slack

Ticket creation from Slack and alerts, onboarding, releases, daily digests and stale-ticket reviews, between Jira and Slack. These are ready-made starting points. Anything else you can describe works too.
The moment it happensAI

Triage support requests into Jira and alert the right Slack channel

Each incoming support request becomes a Jira ticket with a category, priority and summary, and is posted to the Slack channel for that category.

See how it works
The moment it happens

Turn security alerts into Jira tickets and Slack messages

Each security alert creates one Jira ticket, posts to your security channel, and messages the affected person in Slack when the alert names them.

See how it works
The moment it happens

Create onboarding tickets in Jira and welcome new hires in Slack

When a new hire is added, an onboarding epic with tasks appears in Jira, they are invited to the right Slack channels, and the team gets a welcome post.

See how it works
The moment it happens

Update Jira and post release notes to Slack when you tag a release

When a release is tagged, the Jira tickets mentioned in its commits get a fix version and move to Done, and Slack gets the release notes.

See how it works
On a schedule

Post a daily Jira digest in Slack

Each weekday morning Slack shows yesterday's Jira progress grouped by status, plus blockers and what is due soon.

See how it works
The moment it happens

Alert Slack on production errors with one Jira bug per error

Production errors are posted to Slack straight away, and each distinct error opens exactly one Jira bug, with repeats added as comments.

See how it works
Every 5 minutes

Turn Slack requests into Jira issues

Each request posted in your requests channel becomes a Jira issue, and the link is posted back in the thread.

See how it works
On a scheduleAI

Review stale Jira tickets every week in Slack

Every Monday Slack lists Jira tickets that have not moved in 30 days, with a suggestion for each: close it, chase it or keep it.

See how it works
Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with Jira and Slack, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any Jira and Slack automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what should happen between Jira and Slack in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.
  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Post in #sprint any Jira ticket in the current sprint that has been In Progress for more than 3 days without an update, and mention the assignee.

When someone reacts with :ticket: to a Slack message in #help, create a Jira task with the message text, using AI to write a short summary as the title.

Use cases

Why people connect Jira and Slack

How the two apps work together

  • Jira webhooks send issue created, updated and transitioned events to a ClickRuntime trigger link, or the script queries Jira every few minutes.
  • The script posts a formatted message to a Slack channel or DM, often with the issue link and fields.
  • Slack messages or reactions in a channel can reach a trigger link through Slack events and create or update Jira issues.
  • High-priority tickets in the team channel

    Support and engineering leads post new Highest or High priority Jira issues to a Slack channel. The message shows key, summary, reporter and assignee.

  • Daily standup list per person

    Scrum masters send each developer a Slack DM with their In Progress and To Do tickets for the sprint. Standups start with everyone knowing their list.

  • Tickets from Slack requests

    IT and ops teams turn requests posted in a help channel into Jira tickets. The thread gets a reply with the ticket key and link.

  • Sprint progress for managers

    Engineering managers get a Slack summary at sprint end with done, carried over and added tickets. It replaces a manual board review.

More apps

Jira, Slack and other apps in one automation

An automation isn't limited to two apps. Add the next step in another app and it runs as part of the same automation.

PagerDuty incidents create Jira tickets in Slack

When a PagerDuty incident is resolved, create a Jira follow-up ticket for the postmortem and post it in #incidents.

Weekly Jira metrics in Slack and Sheets

Every Monday, add last week's created and resolved Jira ticket counts to my Metrics sheet and post them in #eng-leads.

Zendesk escalations to Jira with Slack alert

When a Zendesk ticket is tagged bug, create a Jira issue with the ticket details and post the link in #support-escalations.

Setup

Connect Jira and Slack once

Every idea on this page uses the same two connections, so you set them up once. If one is missing, your assistant tells you and links to the right place.

Jira

Project management / Issue tracking

  1. Go to id.atlassian.com/manage-profile/security/api-tokens and choose Create API token. Atlassian sends a code to your email to confirm.
  2. Name the token, choose an expiry of 1 to 365 days, create it and copy it straight away. It can't be shown again.
  3. Note your site address, such as yoursite.atlassian.net, and the email of the Atlassian account that created the token.
  4. In the ClickRuntime dashboard, open Connections & secrets and save the email, token and site for Jira.

Slack

Team chat

  1. At api.slack.com/apps, create a new app from scratch in your workspace.
  2. Under OAuth & Permissions, add the bot scopes the automation needs, such as chat:write, channels:read and channels:history.
  3. In the ClickRuntime dashboard, open Connections, choose Slack and enter your app's details, then install it to your workspace.
  4. In each channel the automation should use, type /invite @your-app-name.

FAQ

Questions about connecting Jira and Slack

How does ClickRuntime connect to Jira?
Through your Atlassian account, which you connect in your ClickRuntime dashboard. Tickets are created and updated by that account, in the projects it can access.
Can it post to private Slack channels?
Yes. Invite the ClickRuntime notifications app to the channel. Automations that read messages or invite people use your own Slack app instead.
Will it create duplicate tickets?
Automations that create tickets from alerts or messages remember what they have handled, and the error and security ones check for an open ticket first.
Which Jira project do tickets go to?
The one you choose when setting up each automation, such as SUP for support or SEC for security. Issue types and priorities follow your project's own settings.
Can it mention the Jira assignee in Slack?
Yes, if their Slack account uses the same email address. The script looks up the Slack user by email and mentions them.
Can I filter by project, priority or JQL?
Yes. The script can run any JQL query or check fields on webhook events, so only the tickets you care about are posted.
Does it post every update to a ticket?
No, only what you ask for, such as new tickets, status changes or comments. The rest are ignored.

Tell your assistant what Jira and Slack should do together

Free plan. No credit card.