Eng Team Reporter

Automated activity reports for engineering teams. Pull data from GitHub, JIRA, and Confluence into clear, actionable views — per engineer or per repository.

See example reports

What you get

👤

Per-engineer reports

See each team member's JIRA issues, pull requests, commits, code reviews, and docs updates — all in one place for any date range.

📦

Per-repository reports

Understand what's happening in each repo. PRs grouped by code area, with file-level change breakdowns and JIRA cross-references.

🔗

JIRA cross-referencing

Automatically links PRs and commits back to JIRA tickets — including fuzzy matching when developers forget to tag their work.

📊

At-a-glance summaries

Summary cards show key stats up front: issues created/closed, PRs opened/merged, commits, reviews, and documentation updates.

📝

Confluence tracking

Captures documentation activity too — pages created and updated — so the less visible work doesn't go unnoticed.

📁

Offline HTML reports

Reports are self-contained HTML files. Share them via email, Slack, or drop them in a shared drive. No logins required.

Example reports

Below are anonymised examples showing the type of reports generated. Click through to see the full detail.

Issues 7
PRs 8
Commits 6
Reviews 5
Docs 3
PLAT-2241 - [data-sync] Add logging for API endpoints To Do
platform-core#412 - fix duplicate component results Merged
deploy-config#1801 - fix postsync yaml Merged

Engineer Activity Report

Individual report for Alex Chen — Feb 17-25

View full report
PRs 17
Merged 8
Commits 12
Added +16.9k
Deleted -6.6k
#417 - filter out false positives from password detection Open
#415 - filters for generic passwords Merged
#406 - add data layer for dependency analysis Merged

Repository Activity Report

acme-dev/platform-core — Feb 17-25

View full report
Issues 79
Closed 90
PRs 98
Reviews 249
Docs 125
12 engineers tracked across 8 repositories
108 commits | 685 files changed | +123k / -143k lines
Top reviewer: s.park (48 PRs reviewed)

Team Overview Report

Full team summary — Feb 1-27

View full report

How it works

1

Connect your tools

Point the reporter at your GitHub org, JIRA project, and Confluence space. Configure which teams and repos to track.

2

Choose your date range

Generate reports for any period — a sprint, a week, a month, or a custom range. It's flexible.

3

Get your reports

Out comes a set of self-contained HTML reports — one per engineer, one per repository — ready to share.

Installation

A single binary with no dependencies. Download it and run — no Python, Java, or Node.js required.

Homebrew (macOS)

brew tap zagware/tap brew install eng-team-reporter

Manual download

Grab the latest release for your platform:

macOS (Apple Silicon).tar.gz / .pkg
macOS (Intel).tar.gz / .pkg
Linux (x64).tar.gz
Windows (x64).zip

View releases on GitHub

Quick start

Activate your license:

eng-team-reporter --activate /path/to/license.json

Run the interactive setup wizard to connect GitHub, JIRA, and Confluence:

eng-team-reporter --setup

Generate your first report:

eng-team-reporter --period week

Open the report:

open ~/eng-team-reporter/weekly_report_*.html

Get started

Download Eng Team Reporter and generate your first report in minutes. Contact us for licensing.

Download from GitHub Contact us