GitLab Time Tracking — Use Teetrack Alongside GitLab

Manage your DevOps pipeline in GitLab, track and bill development time in Teetrack.

Track development and issue work in Teetrack alongside GitLab. A manual workflow with time exports; the tools do not transfer data automatically.

Manual workflow with GitLab

Teetrack has no native GitLab integration. This page shows how to use the two tools together in a complementary workflow.

Each Teetrack account belongs to one person. Shared team reports and automatic transfers between these tools are not part of this workflow.

Explore native calendar and MCP connections

Requirements

A GitLab account (SaaS or self-managed) with projects and issues set up
A Teetrack account
Consistent naming between Teetrack projects and GitLab projects

Follow the manual workflow

Step 1: Create Teetrack projects matching your GitLab projects

Set up projects in Teetrack that correspond to your GitLab projects or groups. Use consistent naming to make cross-referencing between tracked time and code work effortless.

Step 2: Start a Teetrack timer when picking up a GitLab issue

When you start working on a GitLab issue or merge request, start a timer in Teetrack with the matching project and a brief description such as the issue title.

Step 3: Reference GitLab issues in Teetrack time entries

Add the GitLab issue number or merge request URL in your Teetrack time entry description so you can match development hours to specific issues during reviews.

Step 4: Compare tracked time with GitLab milestones

Review your Teetrack reports alongside GitLab milestones and boards to assess where development time was spent and calibrate future iteration planning.

What you can do

Track development time per issue or merge request: Log time against specific GitLab issues or merge requests in Teetrack for precise project cost tracking and client billing.
Accurate billing for development engagements: Track billable time in Teetrack and export CSV for your billing workflow. Time spent on features, code reviews, and DevOps work is captured for accurate reporting.
Better iteration planning with real time data: Compare planned time estimates from GitLab with actual tracked time in Teetrack to improve accuracy of future sprints and milestones.

Frequently Asked Questions

Does Teetrack integrate directly with GitLab?

There is no native integration. You use both tools side by side — manage code and DevOps in GitLab and track development time in Teetrack. Reference issue numbers in Teetrack for easy cross-referencing.

GitLab has built-in time tracking. Why use Teetrack?

GitLab time tracking is tied to issues and uses slash commands. Teetrack provides a full time tracking workspace with timers, billable rates, CSV timesheet export, and detailed reporting across all your projects — pair it with your billing tool for the invoicing side.

How do I connect Teetrack entries to GitLab issues?

Add the GitLab issue number (e.g., #87) or the issue URL in your Teetrack time entry description. This makes it easy to match tracked time to issues during reviews.

Can I use this for self-managed GitLab instances?

Yes. Since there is no API connection between the tools, the workflow works with any GitLab setup — SaaS or self-managed.

Can I automate the workflow?

Teetrack has no native Zapier or webhook receiver for GitLab today, so you log time entries manually in Teetrack while referencing the GitLab issue number or merge request URL in the description. If you use an AI assistant, Teetrack’s MCP tools let you start timers or create entries directly from chat without leaving your editor.

Track your development hours in Teetrack while working in GitLab

Start free

Works with GitLab SaaS and self-managed instances.