cmd: task timesheet [x] confusion #3096
Unanswered
rablakesl
asked this question in
Community support
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Good Afternoon!
I am sorry to post this silly question, but I am unsure where else to seek guidance. I have read the task man, researched online, and tested in different environments. I assume I am just not understanding the use of task timesheet in the new version.
I want to provide a little history first: I have been using Task Warrior since 2013. It was one of the first tools I added to my toolbelt when I started my business. Since then I have expanded how I use it and have incorporated / integrated other tools with it to run my business. It's quite an amazing program; thank you!
I have been running my current task environment on CentOS6, and I have wanted to upgrade to the latest OS and Task, so I have moved it over to CentOS8. However, the problem I am experiencing is persistent on other Cent and Debian OS's, but it does not appear in older (i.e. 2.5.0) Task Warrior's.
In the older versions, I use 'task timesheet x' a lot, and i use it in the daily reports that I auto-generate. It will display x weeks in the old timesheet format.
In the new version, 'task timesheet x' behaves a lot differently and I don't understand it and I can't find documentation to explain it.
Example: task timesheet 2 returns ID2 only / task timesheet displays 2 weeks of summary (i.e. without annotations.)
Is this the expected behavior or am I using the command wrong? Or does this indicate an issue with my install? I am wanting to be able to just issue a task timesheet 2 and get 2 weeks in the old format and to also possibly add filters to get results only for x weeks for x project.
I have posted my diag here. I look forward to hopefully hearing from someone who can offer guidance, and I thank you very much in advance!
task diag:
Beta Was this translation helpful? Give feedback.
All reactions