clock doesn't respect org-id-link-to-org-use-id

clock doesn't respect org-id-link-to-org-use-id

[Dave D]

Hi All,

I use org-mode clock table to generate report for the tasks I clocked.
The header of my clock table looks like this:
#+BEGIN: clocktable :block 2021-06-18 :scope agenda :maxlevel 5
:fileskip0 t :link t

I have :link t so that I can jump to a task directly from the clock
table. I have noticed that sometimes the link doesn't work because of
a heading having strange characters ( in my case my heading is
suffixed with date time).

I traced it back to function org-clock-get-table-data, which seems to
construct the link itself from scratch without leveraging the existing
function org-store link. This also results in it not respecting the
value of org-id-link-to-org-use-id. If use org-store-link in
org-clock-get-table-data, a few lines of code can be reduced and the
behavior can be more consistent and robust.

If I'm correct so far, anybody mind work or this? I can do that as
well, but i'm not fluent with lisp or the workflow, so I'd appreciate
if someone else can help.

Thank You.
Dave

Re: clock doesn't respect org-id-link-to-org-use-id

[Ihor Radchenko]

Dave D <wenlong.dai@gmail.com> writes:

> I have :link t so that I can jump to a task directly from the clock
> table. I have noticed that sometimes the link doesn't work because of
> a heading having strange characters ( in my case my heading is
> suffixed with date time).

Thanks for reporting! Could you provide an example of such heading?

> I traced it back to function org-clock-get-table-data, which seems to
> construct the link itself from scratch without leveraging the existing
> function org-store link. This also results in it not respecting the
> value of org-id-link-to-org-use-id. If use org-store-link in
> org-clock-get-table-data, a few lines of code can be reduced and the
> behavior can be more consistent and robust.

Your analysis looks reasonable, but a concrete reproducer would help (at
least to create a test case).

Best,
Ihor