How to generate clock report for hours worked each day?

How to generate clock report for hours worked each day?

[ConcreteVitamin]

[-- Attachment #1: Type: text/plain, Size: 1862 bytes --]

org-clock-report is awesome; however, it reports time spent on each task.
Is there any custom command that you use to generate a clock report *showing
hours worked, across tasks, for each day*?

The trouble I've encountered is that, I file my TODO captures under a
file+datetree entry. For example, one TODO task might be filed on Day -2,
but I could be working on it -- i.e., clocking in and out -- on Day -2, -1,
and today. So generating a table naively will just show something like:

#+BEGIN: clocktable :maxlevel 4 :scope file :block thisweek
#+CAPTION: Clock summary at [2017-09-23 Sat 11:48], for week 2017-W38.
| Headline                              | Time      |         |       |       |
|---------------------------------------+-----------+---------+-------+-------|
| *Total time*                          | *1d 0:12* |         |       |       |
|---------------------------------------+-----------+---------+-------+-------|
| 2017                                  | 1d 0:12   |         |       |       |
| \_  2017-09 September                 |           | 1d 0:12 |       |       |
| \_    2017-09-11 Monday               |           |         |  1:23 |       |
| \_      look into AAA BBBB project    |           |         |       |
| \_    2017-09-15 Friday               |           |         |  3:33 |       |
| \_      look into XXX YYYY project    |           |         |       |  3:33 |
#+END:

Note that the second TODO task was filed under 2017-09-15 Friday, which was
the date I entered the task. But really, I might have worked on it on
Friday, Saturday, etc. I just want another command to show how many hours
I've worked on each day, generating a report such as the following:

2017-09-11 Monday     xx hours yy mins worked (across all tasks)
...
2017-09-15 Friday     zz hours tt mins worked (across all tasks)

Thanks in advance.

[-- Attachment #2: Type: text/html, Size: 6316 bytes --]

Re: How to generate clock report for hours worked each day?

[Matt Lundin]

ConcreteVitamin <concretevitamin@gmail.com> writes:

> org-clock-report is awesome; however, it reports time spent on each
> task. Is there any custom command that you use to generate a clock
> report showing hours worked, across tasks, for each day?
>
> [...]
>
> I just want another command to show how many hours I've worked on
> each day...

You can generate such a report in the daily agenda by activating
org-agenda-clockreport-mode (press R while viewing the agenda). It will
show how much time you clocked during the day, broken down by file,
subtree, etc. You can customize what is shown with the variable
org-agenda-clockreport-parameter-plist.

Best,
Matt

Re: How to generate clock report for hours worked each day?

[ConcreteVitamin]

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]

Thanks, it does show the hours clocked on the current day.  Is there
something on top of this mode that allows me to specify the specific day?
(Better, I just want to quickly show the <lastweek> to see the trend of my
productivity :)).

On Sat, Sep 23, 2017 at 7:04 PM Matt Lundin <mdl@imapmail.org> wrote:

> ConcreteVitamin <concretevitamin@gmail.com> writes:
>
> > org-clock-report is awesome; however, it reports time spent on each
> > task. Is there any custom command that you use to generate a clock
> > report showing hours worked, across tasks, for each day?
> >
> > [...]
> >
> > I just want another command to show how many hours I've worked on
> > each day...
>
> You can generate such a report in the daily agenda by activating
> org-agenda-clockreport-mode (press R while viewing the agenda). It will
> show how much time you clocked during the day, broken down by file,
> subtree, etc. You can customize what is shown with the variable
> org-agenda-clockreport-parameter-plist.
>
> Best,
> Matt
>
>

[-- Attachment #2: Type: text/html, Size: 1420 bytes --]

Re: How to generate clock report for hours worked each day?

[Matt Lundin]

ConcreteVitamin <concretevitamin@gmail.com> writes:

> Thanks, it does show the hours clocked on the current day. Is there
> something on top of this mode that allows me to specify the specific
> day? (Better, I just want to quickly show the <lastweek> to see the
> trend of my productivity :)).

Yes, you can just move back and forward in the agenda with "b" and "f."
Or you can pick a day on the calendar with "j". And you can view your
aggregated time for the week with "vw".

Best,
Matt

Re: How to generate clock report for hours worked each day?

[ConcreteVitamin]

[-- Attachment #1: Type: text/plain, Size: 762 bytes --]

Thanks!  This workflow works.

I can't help but wonder, does my use case show that in org-mode philosophy,
tasks are best filed under a plain entry, not within a datetree?

On Sun, Sep 24, 2017 at 7:35 AM Matt Lundin <mdl@imapmail.org> wrote:

> ConcreteVitamin <concretevitamin@gmail.com> writes:
>
> > Thanks, it does show the hours clocked on the current day. Is there
> > something on top of this mode that allows me to specify the specific
> > day? (Better, I just want to quickly show the <lastweek> to see the
> > trend of my productivity :)).
>
> Yes, you can just move back and forward in the agenda with "b" and "f."
> Or you can pick a day on the calendar with "j". And you can view your
> aggregated time for the week with "vw".
>
> Best,
> Matt
>
>

[-- Attachment #2: Type: text/html, Size: 1200 bytes --]

Re: How to generate clock report for hours worked each day?

[Eric S Fraga]

[-- Attachment #1: Type: text/plain, Size: 906 bytes --]

On Monday, 25 Sep 2017 at 03:58, ConcreteVitamin wrote:
> Thanks!  This workflow works.
>
> I can't help but wonder, does my use case show that in org-mode philosophy,
> tasks are best filed under a plain entry, not within a datetree?

I would say that the org-mode philosophy is what works for you is
perfect!

My own workflow is that I use a date tree for "short" tasks, those that
will be done usually well within a single day's activity.  Longer tasks
are "projects" and they tend to have their own full structure.  E.g. I
have main headlines for teaching, research, and admin and I clock into
those while my date tree will be things like "Meet with student X",
"submit proposal", "prepare agenda for meeting", etc.

But everybody does things differently and that is the best thing about
org: it doesn't impose any particular approach.

-- 
: Eric S Fraga via Emacs 26.0.50, Org release_9.1-64-g657302

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]

Re: How to generate clock report for hours worked each day?

[ConcreteVitamin]

[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]

Following up on this: is there a way to configure such that non-clocked in
files (0:00) are not shown in this table?

On Mon, Sep 25, 2017 at 12:39 AM Eric S Fraga <esflists@gmail.com> wrote:

> On Monday, 25 Sep 2017 at 03:58, ConcreteVitamin wrote:
> > Thanks!  This workflow works.
> >
> > I can't help but wonder, does my use case show that in org-mode
> philosophy,
> > tasks are best filed under a plain entry, not within a datetree?
>
> I would say that the org-mode philosophy is what works for you is
> perfect!
>
> My own workflow is that I use a date tree for "short" tasks, those that
> will be done usually well within a single day's activity.  Longer tasks
> are "projects" and they tend to have their own full structure.  E.g. I
> have main headlines for teaching, research, and admin and I clock into
> those while my date tree will be things like "Meet with student X",
> "submit proposal", "prepare agenda for meeting", etc.
>
> But everybody does things differently and that is the best thing about
> org: it doesn't impose any particular approach.
>
> --
> : Eric S Fraga via Emacs 26.0.50, Org release_9.1-64-g657302
>

[-- Attachment #2: Type: text/html, Size: 1520 bytes --]

Re: How to generate clock report for hours worked each day?

[Eric S Fraga]

[-- Attachment #1: Type: text/plain, Size: 343 bytes --]

On Tuesday, 26 Sep 2017 at 18:27, ConcreteVitamin wrote:
> Following up on this: is there a way to configure such that non-clocked in
> files (0:00) are not shown in this table?

I don't get non-clocked files shown.  What version of org are you using?
Maybe post what you get?

-- 
: Eric S Fraga via Emacs 26.0.50, Org release_9.1-64-g657302

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]

Re: How to generate clock report for hours worked each day?

[ConcreteVitamin]

[-- Attachment #1: Type: text/plain, Size: 721 bytes --]

It looks something like this: https://pastebin.com/bBFwPuwb

This is generated by
$ #+BEGIN: clocktable :maxlevel 0 :scope agenda :step day :tstart "<-1w>"
:tend "<now>" :compact t

I am using Spacemacs.  Are org-plus-contrib-20170918 &
evil-org-20170917.1447 the relevant packages?

On Tue, Sep 26, 2017 at 10:57 PM Eric S Fraga <esflists@gmail.com> wrote:

> On Tuesday, 26 Sep 2017 at 18:27, ConcreteVitamin wrote:
> > Following up on this: is there a way to configure such that non-clocked
> in
> > files (0:00) are not shown in this table?
>
> I don't get non-clocked files shown.  What version of org are you using?
> Maybe post what you get?
>
> --
> : Eric S Fraga via Emacs 26.0.50, Org release_9.1-64-g657302
>

[-- Attachment #2: Type: text/html, Size: 1139 bytes --]

Re: How to generate clock report for hours worked each day?

[Eric S Fraga]

[-- Attachment #1: Type: text/plain, Size: 312 bytes --]

On Thursday, 28 Sep 2017 at 23:43, ConcreteVitamin wrote:
> It looks something like this: https://pastebin.com/bBFwPuwb

Ah, okay, you are using :scope agenda, not :scope file in this case.  I
have no answer to your query then.  Sorry.

-- 
: Eric S Fraga via Emacs 27.0.50, Org release_9.1.1-87-g3c83f1

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]

Re: How to generate clock report for hours worked each day?

[Yasushi SHOJI]

Hi,

On Wed, Sep 27, 2017 at 3:27 AM, ConcreteVitamin
<concretevitamin@gmail.com> wrote:
> Following up on this: is there a way to configure such that non-clocked in
> files (0:00) are not shown in this table?

:fileskip0 t

?
-- 
         yashi