How to send a Jira sprint report to Slack automatically

What are the ways to get a Jira sprint report into Slack?

Last verified: October 25, 2026. Sources: Jira automation triggers, Jira automation actions, Use Slack with Automation, Jira notifications in Slack, Jira sprint report.

How do you build a Jira Automation rule that posts a sprint report?

1. Create a Slack incoming webhook. In Slack, add an incoming webhook for the channel that should receive the report, then copy the webhook URL. If Slack says only certain users can add integrations, a workspace admin has to install it for you (Atlassian).
2. Create a rule in Jira. Go to your space's automation settings and create a new rule.
3. Add the trigger. Choose "Sprint created, started, or completed", set it to completed, and select your scrum board. The trigger can run for every sprint on the board, or you can narrow it with a regular expression.
4. Look up the work items. Add "Lookup work items" with a JQL query. It returns up to 100 work items, available to later actions as {{lookupIssues}}.
5. Send the message. Add "Send Slack message", paste the webhook URL, optionally set #channelname to override the default channel, and write the message with smart values.
6. Test it. Run the rule on a recently completed sprint, or create a test sprint, and check the audit log for errors.

A message template using sprint smart values (Atlassian smart values):

*Sprint report: {{sprint.name}}*
Goal: {{sprint.goal}}
Ended: {{sprint.completeDate}}

*Not finished ({{lookupIssues.size}})*
{{#lookupIssues}}
• <{{url}}|{{key}}> {{summary}} ({{status.name}}, {{assignee.displayName}})
{{/}}

Slack's incoming webhooks accept its link syntax, so <url|text> renders as a link. Check the result in your channel, because formatting can vary by field.

Which JQL queries make a useful sprint report?

With the "Sprint completed" trigger, {{sprint.id}} refers to the sprint that just closed. Useful lookups:

• Carried over: sprint = {{sprint.id}} AND statusCategory != Done
• Done: sprint = {{sprint.id}} AND statusCategory = Done
• Bugs closed: sprint = {{sprint.id}} AND type = Bug AND statusCategory = Done

One lookup per Send Slack message keeps the rule easy to debug. If you need two lists, add a second lookup and message, or post the done count and link to Jira's sprint report for the detail.

How do you send a weekly Jira summary to Slack mid-sprint?

Use the "Scheduled" trigger instead. It runs at a fixed rate, such as every 7 days, or on a cron expression like Monday at 9:00. You can attach a JQL query so the rule acts on matching work items. For a weekly status post, sprint in openSprints() AND project = ABC with a lookup of items not yet done gives the team a Monday list of open work.

Atlassian notes that scheduled rules that fail 10 times in a row are disabled automatically (triggers). If your report stops appearing, check the rule's audit log first.

Is the Jira Cloud for Slack app enough on its own?

For notifications, yes. In a channel, /jira connect subscribes it to a Jira space, and /jira manage lets you filter and pause subscriptions. Space admins can also connect channels from Jira, with JQL-based filtering (Atlassian). That gives a stream of events: created, transitioned, commented. It does not compile a sprint summary, so most teams pair it with an automation rule.

What does an automated Jira message miss?

• Context. A list of keys and statuses does not say why work slipped, what is blocked, or what stakeholders need to decide.
• Size. Lookups return up to 100 work items, and a long list in Slack is hard to read. Summarize counts and link the rest.
• Other tools. If the real status also lives in GitHub pull requests, a Google Sheet, or a client email thread, Jira alone gives a partial picture.

Can an AI agent write the sprint report for you?

Yes, if it can read Jira. Claude Tag documents a Jira and Confluence connection that lets it read and update Jira issues (Claude Tag docs), and it needs a Claude Team or Enterprise plan. Check any other agent's current integration list before you plan around it.

Geniusly does not connect to Jira today. Jira, Stripe, Salesforce, HubSpot, and Confluence are listed as coming soon on our pricing and integrations pages. If your team tracks engineering work in GitHub or Linear, Geniusly can already turn that into a weekly update in Slack. See how to turn a Linear or GitHub week into a stakeholder update. It can also pull a tracker from Google Sheets, and it can run a task once, daily, or weekly.

For the stakeholder-facing format, start from the client status update template.

Try Geniusly free →

Frequently asked questions

Can Jira send a sprint report to Slack automatically?

Yes. Create a Jira Automation rule with the Sprint completed trigger, a Lookup work items action using JQL for that sprint, and a Send Slack message action that posts through a Slack incoming webhook.

How do I send a weekly Jira summary to Slack?

Use the Scheduled trigger in Jira Automation, set it to every 7 days or a cron expression, look up work items with a query such as sprint in openSprints(), and post them with Send Slack message.

What is the difference between Jira Cloud for Slack and Jira Automation?

Jira Cloud for Slack sends event notifications and lets you act on work items from Slack. Jira Automation runs rules you define, so it can compile a summary on a trigger or a schedule and post it to a channel.

How many work items can a Jira Automation lookup return?

Atlassian's documentation says Lookup work items returns up to 100 work items, which you reference with the lookupIssues smart value.

Does Geniusly integrate with Jira?

Not yet. Jira is listed as coming soon on Geniusly's pricing and integrations pages. Geniusly currently connects to Gmail, Google Drive, Google Sheets, Slack, GitHub, Linear, and Google Ads.