Open nkprince007 opened 6 years ago
nkprince007
commented
6 years ago The reason I want this integrated with lab and not use the cited tool is because that adds a huge dependency of node.js into my workflow and has several minor issues with little to no support for debugging. Plus, the cited tool uses phantomjs which is another huge dependency.
zaquestion
commented
6 years ago @nkprince Sounds good to me. Some immediate thoughts
0.13issue, mr, etc is part of the command structure, commands should likely be lab issue time startnkprince007
commented
6 years ago If issue, mr, etc is part of the command structure, commands should likely be lab issue time start
That is a clever suggestion.
storing state between commands would be new territory, not against, just not sure best way to approach
gtt stores the data to an autogenerated file in JSON format. We could do the same thing.
would want some way to explicitly log an amount of time
gtt also provides a way to manually edit data using gtt edit <tracker-id>. We could implement something similar and use the $EDITOR variable to open up the file for edits. However, we'd need some validation and backup procedure to protect the files, like opening up the process in a temporary file and then using atomic save or something like that.
curious if gitlab jira integration allows us to plug into loging time in an external issue tracker.
I'm not sure about this.
zaquestion
commented
6 years ago Quick note, in internal/git we have git.Edit which is what we use for creating an MR or issue. Regarding explicit time tracking I'm just thinking something like lab issue time log 21 1h, verbose but just having some should be enough. Editing the time tracking info seems good as well for cleaning up any over/under tracked time.
zaquestion
commented
6 years ago For self signed certs we talked about storing files in ~/.config/lab/certs, which makes sense. Given this would be state and not config tho, we might take the approach nvim and other programs seems to use and make a ~/.share/lab/time -- I'm not sure what the appropriate uses are for .share or what that looks like cross platform.
mmngreco
commented
4 years ago Hi guys, this feature looks awesome! I will be very happy to see it in the following releases. I would like to give you another point of view in order to show you my using case. I'd like to use something like:
lab issue 21 time spent 1d # today by defult
lab issue 21 time spent -1d # ups I make a mistake
lab issue 21 time spent 1d 01-01-2020 # specify the day
lab issue 21 time estimate 1w
lab issue 21 time reset spent # I'm not sure about this
lab issue 21 time reset estimate # I'm not sure about this
lab issue 21 time pull
lab issue 21 time pushand It will be great the possibility of edit a file with vim.
nkprince007
commented
4 years ago @zaquestion are you working on this or do you mind if I start sometime next week?
I'm a freelancer and I generally track my time with issues and merge requests on GitLab. It'd be really awesome, if we could have something similar to https://github.com/kriskbx/gitlab-time-tracker baked into lab tool itself.
TIME STATS
total estimate: 2d 5h 10m
total spent: 2d 6h 51m 4s
spent: 2d 6h 51m 4s
nkprince007: 2d 6h 36m 2s
undefined: 15m 2s
ISSUES
python-dotenvMERGE REQUESTS
TIME RECORDS