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.

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

Find gaps #6

Open
dsample opened this issue Apr 20, 2020 · 5 comments
Open

Find gaps #6

dsample opened this issue Apr 20, 2020 · 5 comments

Comments

@dsample
Copy link

dsample commented Apr 20, 2020

It would be nice to be able to find gaps in the 'current period', with a command like tempo gaps. That way I could see what I still need to log time against, and it would be particularly helpful when trying to find an hour I've missed somewhere.

@szymonkozak
Copy link
Owner

Currently gaps for the selected day are displayed by highlighting hours like this:

image

So maybe a better idea would be to implement option to list all worklogs from the whole month in the single table (as you proposed in #5), and then you will be able to see all the gaps. What do you think about it? The main problem with this idea could be the size of the table (for long tables it would be necessary to scroll it to find all the gaps)

@dsample
Copy link
Author

dsample commented Apr 20, 2020

It would certainly be good to be able to get all of the details of the whole month, but I think for gaps it would be nice to have a way to find out what I've still got to log, ideally in a way which is easy to copy and paste onto a tempo log ... command to make it easiest to finish my timesheet

@szymonkozak
Copy link
Owner

Hmm, I am not sure if we both understand gaps in the same way. I understand these as a gaps between already logged time (as on the screenshot above the gap between worklogs 184941 and 184942).

So do you mean something like this?

$ tempo gaps # today
13:10-14:00 2020-04-20

$ tempo gaps yesterday
13:10-14:00 2020-04-19

$ tempo gaps this # or another alias for the current month
13:10-14:00 2020-04-19
13:10-14:00 2020-04-20

@dsample
Copy link
Author

dsample commented Apr 20, 2020

Ah, I meant gaps as in the difference between number of hours/time logged, and the number of hours which should have been logged (eg. 7h30m Monday-Friday).

We don't use specific times in the logs, so we shouldn't see gaps between two items on the same day we just put the number of hours in the logs, and make sure it adds up to 7h30m per day.

@szymonkozak
Copy link
Owner

Ok, I get it. This looks like company specific issue. In the company where I work now, the sum of hours on the end of the month is important, and such irregularities (like 6h/8h one day and 10h/8h another day) are normal.

Every company uses tempo in a slightly different way so I am not sure about introducing such feature. I would like the core to remain relatively light.

Maybe there is a space for some compromise, like another option for the tempo ls command, which would display the list of worklogs (from the whole month) in a minimal way like this:

$ tempo ls current -m # or tempo ls this -m, whatever 
2020-04-01: 7h30m/7h30m
2020-04-02: 6h/7h30m
2020-04-03: 7h30m/7h30m
2020-04-04: 0h/0h
...
2020-04-30: 7h30m
Sum: 160h/168h

Or something similar (this is my first idea, maybe there are better options for such list). This could be more universal and you could use this for your use case just grepping what you need:

command | grep -vE '7h30m/7h30m|0h/0h'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants