A monthly work report, the kind HR or a client wants with a bill of services, is mostly copying: commits from one place, tickets and time logs from another, pasted into a document. reportin collects that work from the tools where it already happened and writes the report.
reportin
Turn Git and issue-tracker logs into monthly work reports.
Commits, tickets and time entries in, a PDF report out.
ProductsWeb appNuxt, FastAPI, PostgreSQLClosed source, not public yet
The problem
How it works
Connect the sources once:
| Source | What it reads |
|---|---|
| GitHub, GitLab, any Git repository | commits, branches and pull requests, categorized by project |
| Linear, Jira | issues, time logs and sprints, mapped to billable activities |
Then pick a period. The screenshots below use made-up data. reportin aggregates the month's work, drafts the report with a language model, and opens it in an editor next to a chat for asking changes ("add a Next month section with the open tickets"). Every entry links back to the commit or ticket it came from, so the report can be checked line by line. Export is a PDF: a worklog and a bill of services.
Project categories, team members and reporting periods are optional configuration. Teams share workspaces.
Status
Closed source, and not publicly hosted at the moment.
-
Start: generate a monthly report from the connected sources. -
The same report in preview, as it is exported to PDF. -
History of generated reports, drafts and finals. -
Integrations: connect each source once.
