> On Apr 6, 2025, at 11:14 AM, Rohit Patnaik <quanti...@quanticle.net> wrote:
>
> Ah, sorry for the noise, I figured out what my problem was. I'd tried
> specifying :tstart and :tend, per the manual, but my initial attempt to do so
> resulted in the following error:
>
> org-clock-get-table-data: Wrong type argument: stringp, <2025-04-06
>
> However, after rereading the manual more closely, I realized that I'd
> forgotten
> to quote the time strings. Specifying:
>
> #+BEGIN: clocktable :scope file :maxlevel 2 :tstart "<2025-04-06 Sun>"
> :tend "<2025-04-12 Sat>"
>
> got me the result I was looking for.
>
> Thanks,
> Rohit
>
I do the same thing for work to track our jira sprints. Here are a couple
examples I find useful in addition to the two week range.
The first one enables the links so I can quickly see why a particular task
seems high ( forgot to clock out)
#+BEGIN: clocktable :scope file :maxlevel 4 :link t :tstart "[2025-03-22 Sat
00:00]" :tend "[2025-04-05 Sat 11:00]" :formula %
The second one disables the links but shows it broken down by day skipping days
with no logged time. Great for seeing how much time I worked for each day.
#+BEGIN: clocktable :scope file :maxlevel 6 :link nil :tstart "[2025-03-22 Sat
00:00]" :tend "[2025-04-05 Sat 00:00]" :formula % :step day :stepskip0 t
