-
Vinnie Okada authored
Make the following changes to deal with new behavior in Rails 4.1.2: * Use nested resources to avoid slashes in arguments to path helpers.
Vinnie Okada authoredMake the following changes to deal with new behavior in Rails 4.1.2: * Use nested resources to avoid slashes in arguments to path helpers.
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 lets you:
- 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.
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.
How to enter data
Time Tracking uses two [slash commands] that GitLab introduced with this new
feature: /spend and /estimate.
Slash commands can be used in the body of an issue or a merge request, but also in a comment in both an issue or a merge request.
Below is an example of how you can use those new slash commands inside a comment.
Adding time entries (time spent or estimates) is limited to project members.
Estimates
To enter an estimate, write /estimate, followed by the time. For example, if
you need to enter an estimate of 3 days, 5 hours and 10 minutes, you would write
/estimate 3d 5h 10m.
Every time you enter a new time estimate, any previous time estimates will be 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_estimation.