Hello, Michael Alan Dorman <mdor...@jaunder.io> writes:
> Given the following document: > > * TODO Thingy > ** TODO Sub-Thingy 1 > :LOGBOOK: > CLOCK: [2017-07-12 Wed 07:15]--[2017-07-12 Wed 07:25] => 0:10 > :END: > ** DONE Sub-Thingy 2 > :LOGBOOK: > CLOCK: [2017-07-12 Wed 07:25]--[2017-07-12 Wed 07:31] => 0:06 > :END: > > I would previously get a clocktable like (simulated): > > #+BEGIN: clocktable > #+CAPTION: Clock summary at [2017-07-12 Wed 07:32] > > | Headline | Time | | > |-----------------------+--------+------| > | *Total time* | *0:16* | | > |-----------------------+--------+------| > | TODO Thingy | 0:16 | | > | \_ TODO Sub-Thingy 1 | | 0:10 | > | \_ DONE Sub-Thingy 2 | | 0:06 | > #+END: > > Starting with (I believe) org 9.05, I get > > #+BEGIN: clocktable > #+CAPTION: Clock summary at [2017-07-12 Wed 07:32] > > | Headline | Time | | > |------------------+--------+------| > | *Total time* | *0:16* | | > |------------------+--------+------| > | Thingy | 0:16 | | > | \_ Sub-Thingy 1 | | 0:10 | > | \_ Sub-Thingy 2 | | 0:06 | > #+END: > > I don't see any note of this in ORG-NEWS, so I assume it's a > regression. I haven't had a chance to really dig into it yet. This doesn't ring a bell. Anyway, the current behaviour sounds right, since you can get TODO state with the "TODO" special property anyway. Regards, -- Nicolas Goaziou