Easy

Jira Standup Report Generator

Generate daily standup reports from Jira issue data. See what each team member completed, is working on, and what is blocked.

Works with:JiraJira

Free to start

1,000 credits included

No credit card required

Try this agent Book a demo

Setup in 5 min · Cancel anytime

Setup time

~5 min

Time saved

15 min/standup

Difficulty

Easy

Tools

1 connected

How it works

1

Track Completions

Finds all issues moved to Done or In Review in the last 24 hours grouped by who completed them

2

Show Current Work

Lists every In Progress issue per team member so everyone knows what is being worked on today

3

Surface Blockers

Identifies blocked issues and gets details on what is causing the impediment from issue context

4

Team Summary

Generates an overview with completion counts, in-progress totals, and flags for stalled or unstarted work

Try asking

Generate a standup report for the ENG project
What did the PLAT team complete yesterday and what are they working on today?
Show me the standup update for the MOBILE team, focus on blocked items

View the agent prompt

See the full instructions this agent runs on — copy, edit, or customize it

Expand

The Prompt

Task

Use @Jira/Search IssuesName it "Jira/Search Issues" and call it with @Jira/Search Issues to find recently updated issues grouped by assignee, then use @Jira/Get IssueName it "Jira/Get Issue" and call it with @Jira/Get Issue to get details on status changes and blockers. Generate a formatted standup report showing what each team member completed yesterday, is working on today, and what is blocked.

Input

The user provides:

  1. Their Jira project key (e.g., "ENG", "PLAT")
  2. The team or board name (optional)
  3. The time window (optional, defaults to last 24 hours for "yesterday" and current sprint for "today")
  4. Specific team members to include (optional, defaults to all assignees in the project)

Example: "Generate a standup report for the ENG project"

Context

Recent Activity Discovery

  1. Use @Jira/Search IssuesName it "Jira/Search Issues" and call it with @Jira/Search Issues for issues completed yesterday:
    • project = [PROJECT] AND status changed to "Done" AFTER -1d
  2. Use @Jira/Search IssuesName it "Jira/Search Issues" and call it with @Jira/Search Issues for issues currently in progress:
    • project = [PROJECT] AND status = "In Progress" AND sprint in openSprints()
  3. Use @Jira/Search IssuesName it "Jira/Search Issues" and call it with @Jira/Search Issues for blocked issues:
    • project = [PROJECT] AND (status = "Blocked" OR labels = "blocked" OR labels = "impediment") AND sprint in openSprints()
  4. Use @Jira/Search IssuesName it "Jira/Search Issues" and call it with @Jira/Search Issues for issues recently moved to review:
    • project = [PROJECT] AND status changed to "In Review" AFTER -1d

Per-Assignee Grouping

  1. Group all discovered issues by their assignee
  2. For each assignee, categorize issues into:
    • Completed: Issues moved to Done in the last 24 hours
    • In Progress: Issues currently being worked on
    • In Review: Issues submitted for review
    • Blocked: Issues with blocked status or impediment labels
  3. Use @Jira/Get IssueName it "Jira/Get Issue" and call it with @Jira/Get Issue on blocked items to understand the blocking reason from description, comments, or linked issues

Standup Report Structure

For each team member, generate three sections:

  1. Done (Yesterday): What they completed or moved to review
  2. Doing (Today): What they are currently working on
  3. Blocked: Any impediments preventing progress, with details on what is blocking them

Additional Context

  • Flag team members with no activity in the last 24 hours
  • Highlight issues that have been In Progress for more than 3 days
  • Note any high-priority items that are not yet started

Output

Daily Standup Report Project: [Project Key] Date: [Today's Date] Sprint: [Current Sprint Name]


[Team Member 1 Name]

Done:

  • [PROJ-123] [Issue title] - moved to Done
  • [PROJ-124] [Issue title] - submitted for review

Doing:

  • [PROJ-125] [Issue title] - [brief status note]

Blocked:

  • [PROJ-126] [Issue title] - blocked by [reason]

[Team Member 2 Name]

Done:

  • [No completed items yesterday]

Doing:

  • [PROJ-130] [Issue title] - in progress (3 days)

Blocked:

  • None

Team Summary:

  • Completed yesterday: [X] issues
  • Currently in progress: [X] issues
  • Blocked: [X] issues
  • Team members with no activity: [names]
  • High-priority items not started: [count]

WHAT ARE YOU WAITING FOR?

Ready to build?

Stop duct-taping tools.

Stop writing playbooks no one follows.

Start building agents that actually do the work—and do it well.

Cotera: For people who think busywork is boring.

"This is the best product ever when it comes to shipping. Ten on ten recommended. I just can't wait to see what happens with this product."

Rebecca Blount

Director, Customer Success