2019-12-26 22:10:19 +05:30
---
type: reference
disqus_identifier: 'https://docs.gitlab.com/ee/workflow/time_tracking.html'
2020-06-23 00:09:42 +05:30
stage: Plan
group: Project Management
2021-02-22 17:27:13 +05:30
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
2019-12-26 22:10:19 +05:30
---
# Time Tracking
> Introduced in GitLab 8.14.
Time Tracking allows you to track estimates and time spent on issues and merge
requests within GitLab.
## Overview
Time Tracking allows you to:
- Record the time spent working on an issue or a merge request.
- Add an estimate of the amount of time needed to complete an issue or a merge
request.
2021-06-08 01:23:25 +05:30
- View a breakdown of time spent working on an issue or a merge request.
2019-12-26 22:10:19 +05:30
You don't have to indicate an estimate to enter the time spent, and vice versa.
Data about time tracking is shown on the issue/merge request sidebar, as shown
below.
2021-06-08 01:23:25 +05:30
![Time tracking in the sidebar ](img/time_tracking_sidebar_v13_12.png )
2019-12-26 22:10:19 +05:30
## How to enter data
2021-04-29 21:17:54 +05:30
Time Tracking uses two [quick actions ](quick_actions.md ): `/spend` and `/estimate` .
2019-12-26 22:10:19 +05:30
2021-04-29 21:17:54 +05:30
If you use either quick action more than once in a single comment, only the last occurrence is applied.
2019-12-26 22:10:19 +05:30
Below is an example of how you can use those new quick actions inside a comment.
![Time tracking example in a comment ](img/time_tracking_example_v12_2.png )
2021-04-17 20:07:23 +05:30
Adding time entries (time spent or estimates) is limited to project members
with [Reporter and higher permission levels ](../permissions.md ).
2019-12-26 22:10:19 +05:30
### Estimates
To enter an estimate, write `/estimate` , followed by the time. For example, if
2021-04-29 21:17:54 +05:30
you need to enter an estimate of 1 month, 2 weeks, 3 days, 4 hours and 5 minutes,
write `/estimate 1mo 2w 3d 4h 5m` .
Check the [time units you can use ](#configuration ).
2019-12-26 22:10:19 +05:30
2021-02-22 17:27:13 +05:30
Every time you enter a new time estimate, any previous time estimates are
2019-12-26 22:10:19 +05:30
overridden by this new value. There should only be one valid estimate in an
issue or a merge request.
To remove an estimation entirely, use `/remove_estimate` .
### Time spent
2021-06-08 01:23:25 +05:30
To enter time spent, write `/spend` , followed by the time. For example, if you need
2021-04-29 21:17:54 +05:30
to log 1 month, 2 weeks, 3 days, 4 hours and 5 minutes, you would write `/spend 1mo 2w 3d 4h 5m` .
Time units that we support are listed at the bottom of this help page.
2019-12-26 22:10:19 +05:30
2021-02-22 17:27:13 +05:30
Every new time spent entry is added to the current total time spent for the
2019-12-26 22:10:19 +05:30
issue or the merge request.
2021-02-22 17:27:13 +05:30
You can remove time by entering a negative amount: for example, `/spend -3d` removes three
2019-12-26 22:10:19 +05:30
days from the total time spent. You can't go below 0 minutes of time spent,
2021-02-22 17:27:13 +05:30
so GitLab automatically resets the time spent if you remove a larger amount
2019-12-26 22:10:19 +05:30
of time compared to the time that was entered already.
2021-06-08 01:23:25 +05:30
You can log time in the past by providing a date after the time.
2021-04-29 21:17:54 +05:30
For example, if you want to log 1 hour of time spent on the 31 January 2021,
you would write `/spend 1h 2021-01-31` . If you supply a date in the future, the
command fails and no time is logged.
2019-12-26 22:10:19 +05:30
To remove all the time spent at once, use `/remove_time_spent` .
2021-06-08 01:23:25 +05:30
## View a time tracking report
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/271409) in GitLab 13.12.
You can view a breakdown of time spent on an issue or merge request.
To view a time tracking report, go to an issue or a merge request and select **Time tracking report**
in the right sidebar.
![Time tracking report ](img/time_tracking_report_v13_12.png )
The breakdown of spent time is limited to a maximum of 100 entries.
2019-12-26 22:10:19 +05:30
## Configuration
The following time units are available:
- Months (mo)
- Weeks (w)
- Days (d)
- Hours (h)
- Minutes (m)
Default conversion rates are 1mo = 4w, 1w = 5d and 1d = 8h.
2021-03-11 19:13:27 +05:30
### Limit displayed units to hours **(FREE SELF)**
2019-12-26 22:10:19 +05:30
2020-03-13 15:44:24 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/29469/) in GitLab 12.1.
2019-12-26 22:10:19 +05:30
In GitLab self-managed instances, the display of time units can be limited to
hours through the option in **Admin Area > Settings > Preferences** under **Localization** .
With this option enabled, `75h` is displayed instead of `1w 4d 3h` .
## Other interesting links
2021-06-08 01:23:25 +05:30
- [Time Tracking solutions page ](https://about.gitlab.com/solutions/time-tracking/ )
- Time Tracking GraphQL references:
- [Connection ](../../api/graphql/reference/index.md#timelogconnection )
- [Edge ](../../api/graphql/reference/index.md#timelogedge )
- [Fields ](../../api/graphql/reference/index.md#timelog )
- [Group Timelogs ](../../api/graphql/reference/index.md#grouptimelogs )