Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Issue time spent / time estimate #68

Closed
MrSnoozles opened this issue Apr 16, 2018 · 3 comments
Closed

Issue time spent / time estimate #68

MrSnoozles opened this issue Apr 16, 2018 · 3 comments

Comments

@MrSnoozles
Copy link

Hello,

I was looking for a way to add time estimates and spent times for issues through the API. I could find methods to add time for merge requests, but not for individual issues so I guess it is not implemented. Is that right?

If so, would you need help implementing it? I guess it would take me some time though to understand how this library works, but I'd be happy to help.

The relevant documentation can be found here
https://docs.gitlab.com/ee/api/issues.html#add-spent-time-for-an-issue

Regards
Alex
@jdalrymple
Copy link
Owner

Yup! I must of missed that. Easy thing to add, shouldnt take me more than a minute :)

jdalrymple added a commit that referenced this issue Apr 16, 2018
@jdalrymple
- Added addTimeEstimate, addTimeSpent, timeStats, resetTimeSpent and …
aeb4cb4 
…resetTimeEstimate to the Issues API. Requested in PR [#68](#68)

**Breaking Change**

- Renamed timeEstimate to addTimeEstimate, and timeSpend to addTimeSpent, in the MergeRequests API
@jdalrymple
Copy link
Owner

Merged and published :) hope this helps!

@MrSnoozles
Copy link
Author

Write an issue before going to bed, have a solution when you wake up. This is like Christmas for developers.

Thank you so much. From what I could test it seems to be working splendidly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jdalrymple @MrSnoozles