4 commits

Author	SHA1	Message	Date
Robert Speicher	3e4b45fc21	Only include the user's ID in the time_spent command's update hash ... Previously, this would include the entire User record in the update hash, which was rendered in the response using `to_json`, erroneously exposing every attribute of that record, including their (now removed) private token. Now we only include the user ID, and perform the lookup on-demand.	2017-12-19 15:45:08 -06:00
Rémy Coutable	4cfa5ce4a9	Enable the Style/PreferredHashMethods cop ... Signed-off-by: Rémy Coutable <remy@rymai.me>	2017-06-02 19:11:26 +02:00
Timothy Andrew	519bac658a	Fix time tracking endpoints for API v4 ... - Use issue/merge_request IID instead of ID - Duplicate the original `TimeTrackingEndpoints` concern (+ specs) for V3, since this is a breaking change.	2017-03-07 13:56:00 +05:30
Ruben Davila	0f3c9355c1	Add some API endpoints for time tracking. ... New endpoints are: POST :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/time_estimate" POST :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/reset_time_estimate" POST :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/add_spent_time" POST :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/reset_spent_time" GET :project_id/(issues|merge_requests)/(:issue_id|:merge_request_id)/time_stats"	2017-01-18 10:48:16 -06:00