Preparing sprint retrospectives

Embedding live GitHub data in your sprint retrospective pages means your team can review what actually happened during the sprint - PRs, issues, security alerts, commits, and more - without leaving Confluence.

Pull Request information

Paste a link to any pull request to show its state, title, author, labels, and created date:

CODE

https://github.com/{owner}/{repo}/pull/{number}

Pull Requests list

Paste the pulls URL to show all PRs with a Load more button for pagination. Use URL Parameters in the macro config to narrow the list - for example, to show only closed PRs from the sprint period:

CODE

state=closed&sort=updated&direction=desc

Issues list

Paste the issues URL to show all open issues with pagination:

CODE

https://github.com/{owner}/{repo}/issues

Use the URL Parameters field to filter. Supported parameters:

Parameter	Description
`milestone`	Filter by milestone number, `*` (any), or `none` (unassigned)
`assignee`	Filter by username; `none` for unassigned, `*` for any
`labels`	Comma-separated label names
`sort`	`created` (default), `updated`, or `comments`
`direction`	`desc` (default) or `asc`
`since`	Only show items updated after this ISO 8601 timestamp

Milestone information

Show sprint milestone progress - percentage complete and open/closed issue counts:

CODE

https://github.com/{owner}/{repo}/milestone/{number}

Commits - what was shipped

CODE

https://github.com/{owner}/{repo}/commits/{branch}

Compare - sprint summary diff

Show exactly what changed between the sprint start and end, with files changed and +/- stats:

CODE

https://github.com/{owner}/{repo}/compare/{start-tag}...{end-tag}

This is particularly effective when your team tags commits at the start and end of each sprint.

Discussions

If your team uses GitHub Discussions for async retro input, embed a discussion list or specific discussion:

CODE

https://github.com/{owner}/{repo}/discussions

Discussions require the Discussions (read) GitHub App permission. See Working with Discussions for setup.

Security alerts

Reference open security vulnerabilities alongside delivery data to give the team a complete picture of sprint health. See Working with Security alerts for details and permission requirements.

Live reporting macros

For a data-driven retrospective, add the reporting macros directly to your retro page:

PR Cycle Time report - was delivery slowing down or speeding up this sprint?
PR Throughput report - how many PRs were merged vs. opened?
Review Latency report - were PRs getting reviewed quickly enough?

Updated: 12 Jun 2026