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

aggregate calculates wrong time if used with --current #293

Closed
ybc37 opened this issue Jul 4, 2019 · 2 comments
Closed

aggregate calculates wrong time if used with --current #293

ybc37 opened this issue Jul 4, 2019 · 2 comments

Comments

@ybc37
Copy link
Contributor

ybc37 commented Jul 4, 2019

If aggregate is used with --current and it takes more than the current day into account, the calculation of the current aggregated day is wrong.
Example:

$ watson status
Project xy started 2 hours ago (2019.07.04 10:26:45+0200)


$ watson log -dc
Thursday 04 July 2019 (2h 17m 31s)
        current  10:26 to 12:44   2h 17m 31s  xy


$ watson report -dc
Thu 04 July 2019 -> Thu 04 July 2019

xy - 2h 17m 50s


$ watson aggregate -c --from 2019-07-03
Wed 03 July 2019 - 7h 17m 42s
  xy - 7h 17m 42s

Thu 04 July 2019 - 4h 36m 51s
  xy - 4h 36m 51s

Expected result of Thu 04 July 2019: 2h 17m ??s
Expected result of Thu 04 July 2019: 4h 36m 51s

@jmkerr
Copy link
Contributor

jmkerr commented Jul 8, 2019

The current frame is added once for every day the report is generated.

@ybc37
Copy link
Contributor Author

ybc37 commented Jul 9, 2019

Thanks for looking at it!

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

No branches or pull requests

3 participants