Guide
Automated standup reports from Jira and GitHub
Standup bots ask everyone the same three questions in Slack, and people answer from memory. But the answers already exist: tickets moved, PRs merged, blockers were said out loud in yesterday's call. An automated standup report writes itself from that.
Updated October 10, 2026 · 4 min read · By the Align team
What goes in a good standup report
- Done: tickets moved to Done and PRs merged since yesterday, with links.
- Today: what's in progress and what was committed to in the last call.
- Blocked: tickets marked blocked, and blockers someone mentioned, with how long they've been stuck.
- Nothing invented: every line points at a ticket, a PR or a quote.
Standup bot vs automated report
| Standup bot (Geekbot, Standuply) | Automated report | |
|---|---|---|
| Who writes it | Each person, every day | Drafted from Jira, GitHub and the call |
| Accuracy | From memory | From what actually changed |
| Blockers | Only if someone types them | From blocked tickets and what was said |
| Time per person | 2 to 5 minutes | A glance to confirm |
Keep the meeting, shorten it
With the report done before the call, the standup becomes 10 minutes about blockers instead of 20 minutes of status. Some teams go fully async and only meet when a blocker needs people in a room.
How Align does this for you
Align drafts each person's standup every morning from Jira or Linear, GitHub and yesterday's call: what shipped, what's next, who's blocked and for how long. Each line links to its ticket or PR. You can post it to Slack, and the Meet extension shows the team's cards before you press Start.
Frequently asked questions
Does it replace the standup meeting?
It replaces the status part. Many teams keep a short call for blockers, or go async and meet only when something is stuck.
Where does the report come from?
Ticket moves in Jira or Linear, pull requests and merges in GitHub, and commitments and blockers from the last standup call, if you capture it with Align.