How I turned GitLab spent time into client-ready reports

I built a GitLab time-reporting tool because exporting spent time into client reports was painful

We already tracked work and logged time in GitLab, so the raw data was there.

The problem was everything that came after that.

Whenever we needed to prepare a report — for a client, for internal reporting, or just to understand where time went — the process was much more manual than it should have been. We had to pull time entries from GitLab, filter them by project and date range, clean them up, and turn them into something a client or manager could actually read.

It wasn’t impossible, just repetitive and annoying.

So I built Time Track Reporter.

The goal was simple: take the spent-time data that already exists in GitLab and turn it into a clean report without the usual export → spreadsheet → cleanup workflow.

The final report is available in either .csv format (which can be later uploaded to other systems) or .xlsx format (this format is more convenient for visualizing the overall picture).

I also added the ability to retrieve reports from Jira, but this option isn't very popular.

The application is available at the link https://timetrackreporter.com/

What Time Track Reporter does

• pulls spent time data from GitLab

• lets you filter it by project / date range / team member

• turns it into a report that’s easier to review and share

• removes a lot of the manual cleanup that usually happens before reporting

Who I think it’s for

Right now I think it’s most relevant for:

• agencies and outsourced dev teams

• PMs / delivery managers

• teams that already log time in GitLab

• anyone who needs to regularly turn GitLab time entries into reports for clients or management

Why I built it

The main reason is that GitLab already had the data, but not the reporting workflow I wanted.

I didn’t want another spreadsheet-heavy process every time I needed to answer questions like:

• how much time was spent this month?

• who logged time on which project?

• what should go into the client report?

I wanted something that sits between “time was tracked” and “the report is ready”.

What I’m looking for now

I’d love feedback from people who already use GitLab and have to report on time regularly.

If you track time in GitLab:

• how are you turning that into reports today?

• do you do it for clients, internal reporting, or both?

• what’s the most annoying part of the process?

If this sounds close to your workflow, I’d be happy to get honest feedback.