[org-syntax] Should we support active timestamps in clock elements? (was: Bug: Clock date range with the enclosing markup <> are not fully supported [9.4.4 (9.4.4-27-gb712b9-elpaplus)])

[Ihor Radchenko <yantar92@posteo.net>]

Firmin Martin <firmin.martin@ens-lyon.fr> writes:

> Below is a minimal not working example.
>
> 1. In ~/test.org, put the following content.
>
> * TODO Task
>   SCHEDULED:<2021-03-13 sam. ++1d>
>   :PROPERTIES:
>   :Effort:   1:00
>   :LAST_REPEAT: [2021-03-12 ven. 12:39]
>   :END:
>   :LOGBOOK:
>   - State "DONE"       from "TODO"       [2021-03-12 ven. 12:39]
>   CLOCK: <2021-03-12 ven. 09:15>--<2021-03-12 ven. 12:15> =>  3:00
>   :END:
>
> 2. Insert the dynamic clock table and press C-c C-c on it
>
> #+BEGIN: clocktable :scope ("~/test.org") :maxlevel 8 :block 2021-03-12
> #+END:
>
> the task does not show up. 

Sorry for the late reply.

Active timestamps are indeed not supported in clock lines. Only inactive
timestamps are currently allowed.
See https://orgmode.org/worg/dev/org-syntax.html#Clocks

Dear All,
Should we allow active timestamps in clocks? It sounds reasonable.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>