1. 16 Aug, 2018 1 commit
  2. 09 Jul, 2018 1 commit
  3. 13 Jun, 2018 1 commit
  4. 31 May, 2018 1 commit
  5. 30 May, 2018 1 commit
  6. 24 May, 2018 1 commit
  7. 09 May, 2018 1 commit
  8. 04 Jan, 2018 1 commit
  9. 22 Dec, 2017 1 commit
  10. 19 Dec, 2017 1 commit
    • Robert Speicher's avatar
      Only include the user's ID in the time_spent command's update hash · 3e4b45fc
      Robert Speicher authored
      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.
      3e4b45fc
  11. 20 Oct, 2017 1 commit
  12. 12 Oct, 2017 1 commit
  13. 22 Aug, 2017 1 commit
  14. 09 Aug, 2017 1 commit
  15. 04 Aug, 2017 1 commit
  16. 02 Aug, 2017 1 commit
  17. 27 Jul, 2017 1 commit
  18. 21 Jul, 2017 1 commit
  19. 28 Jun, 2017 3 commits
  20. 06 Jun, 2017 1 commit
  21. 13 Mar, 2017 1 commit
  22. 07 Mar, 2017 2 commits
  23. 20 Feb, 2017 1 commit
  24. 18 Jan, 2017 1 commit
    • Ruben Davila's avatar
      Add some API endpoints for time tracking. · 0f3c9355
      Ruben Davila authored
      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"
      0f3c9355
  25. 20 Dec, 2016 2 commits
  26. 17 Aug, 2016 2 commits
  27. 10 Aug, 2016 1 commit
  28. 14 Jan, 2016 1 commit