Timeglass for GitLab Issues
Timeglass captures the work behind GitLab issues as it moves through code, merge requests, pipelines, and release checks. Engineers keep their normal workflow while each person gets a private time entry to review.
14-day free trial. No credit card required.
GitLab10:12amReporting performance · Milestone 12.4
In progressReporting performance · Milestone 12.4
Ready to reviewThe missing piece
Project management tools keep tasks, owners, and deadlines organized. The hours often end up in a separate timer or a spreadsheet filled in from memory. Timeglass connects the plan to the real workday and drafts the record while the context is still clear.
How it works
Timeglass brings your tasks and your workday into the same record, while each person stays in control of what they approve.
Continue using issues, epics, and milestones to organize delivery. Timeglass keeps the issue and project context available while the engineering work continues.
GitLabReporting performance · Milestone 12.4Current taskAn issue may span the Web IDE, local code, merge request comments, pipeline logs, and Slack decisions. Timeglass gathers that activity before drafting the entry.
GitLabVS CodeGitLab merge requestsGitLab CI/CDTimeglass drafts a clear entry with the project, description, and duration already filled in. The person who did the work can check it, make any changes, and approve it.
Optimized the export worker and added queue latency metrics
Reporting performance · Milestone 12.4The whole task, captured
A reliable time entry needs more than the minutes spent looking at one task page. Timeglass follows the related work across the apps your team already uses, then keeps the evidence together in one private daily record.
Nothing is shared until the person who did the work reviews it.
GitLabWhat teams use it for
Once the hours are attached to the right work, project plans can be compared with what delivery actually required.
Connect coding, testing, review, and release time to the issue and milestone used for planning the work.
See the time taken by dependencies, infrastructure, security fixes, and recurring technical upkeep during each milestone.
Keep engineering hours tied to the right customer or statement of work when several repositories support the same engagement.
Simple setup
Create a Timeglass workspace, add the desktop app, and invite your team. Timeglass starts drafting entries from the workday and keeps the GitLab Issues task context attached.
Questions about GitLab Issues time tracking
No. Timeglass runs alongside GitLab Issues and drafts time from the workday. Your team can keep using the task setup they already have without adding another timer to every item.
No. Timeglass records work in the background, so forgetting to start a timer does not create a blank space in the timesheet. Each person reviews the result before it is shared.
Yes. Work that starts in GitLab Issues may continue in documents, meetings, messages, design files, code, or browser tabs. Timeglass includes that surrounding activity when it drafts the entry.
Yes. Each person sees and approves their own drafted entries. They can change the project, description, or duration before the time is released to a manager.
Yes. Approved time can be grouped by client, project, person, or activity so managers can compare actual effort with plans, budgets, and delivery targets.
GitLabTimeglass for GitLab Issues
Give your team a normal workday and get an accurate project record at the end of it.
14-day free trial. No credit card required.