All workflows
Jira logoAnthropic logoSlack logo

Daily Jira status report to Slack

Counts your Jira tickets by status every morning and posts the breakdown to Slack, with a short read on what stands out.

Every day at 08:303 apps3 steps

Apps it connects

Authenticate each one once and the workflow is ready to run.

What it does

The integration steps this workflow runs, in the order it first runs them.

  1. 1JiraSearch issues
  2. 2AnthropicGenerate model response
  3. 3SlackSend message

How it works

Everything the template sets up, and what to fill in before the first run.

Every morning this posts one Slack message with how many Jira tickets sit in each of the three status categories — To Do, In Progress and Done — broken down by the status names your project actually uses, and split by assignee.

It runs one Jira search per category and buckets on the status category rather than the status name, so a project whose columns are called "Triage", "In Review" and "Shipped" is counted correctly without being configured first. Each search pages through Jira rather than taking the first hundred results: Jira returns at most 100 issues per call and never a total, so a single call would report "100 To Do" for every team with a backlog, which is the one number this report exists to get right. Each search stops at maxPagesPerStatus pages (ten by default, so a thousand issues); a count that hit that ceiling is printed with a trailing + and the message says so, rather than passing a floor off as a total.

Done is a rolling window — the last seven days by default, since an all-time completed count only ever goes up and says nothing about this morning. It matches issues resolved inside the window, and, for the many projects that close issues without ever setting a resolution, issues in a Done status that moved inside the window. Set doneLookbackDays to 0 for the all-time count instead.

Claude reads the finished figures and adds up to three lines on what stands out — work piling up in one column, a queue concentrated on one person, a backlog growing while nothing ships. It is given the numbers and asked to comment on them; it is never asked to produce one, so the figures in the message are always the counted ones. If Claude has nothing worth saying it says so and the section is left out, and if the Anthropic call fails the report still goes out with its numbers intact.

Set the Slack channel before the first run. Leave jiraProjectKey blank to count every project your Jira connection can see, or set it to a project key such as PROJ to scope the report to one board.

jiraslackaidailyreportingstatus updatestandupproject management

Start from a workflow that already works.

Add "Daily Jira status report to Slack" to your workspace, connect its apps, and make it yours. No credit card required.

Free plan available · No credit card required