Examples:
* Top-Heading
** TODO Here I invoke org-todo to DONE
:PROPERTIES:
:TRIGGER: 2017-12-03-target(TODO)
:END:
** This should be changed to TODO
:PROPERTIES:
:ID: 2017-12-03-target
:END:
... this is working (i.e., "This should be changed to TODO" gets its
TODO keyword).
* Top-Heading with process indicator [0/2]
** TODO Here I invoke org-todo to DONE
:PROPERTIES:
:TRIGGER: 2017-12-03-target(TODO)
:END:
** This should be changed to TODO
:PROPERTIES:
:ID: 2017-12-03-target
:END:
... this is *not* working.
However, anticipating the wrong position:
* Top-Heading with process indicator [0/2]
:PROPERTIES:
:TRIGGER: 2017-12-03-target(TODO)
:END:
** TODO Here I invoke org-todo to DONE
:PROPERTIES:
:TRIGGER: 2017-12-03-target(TODO)
:END:
** This should be changed to TODO
:PROPERTIES:
:ID: 2017-12-03-target
:END:
... is working. And according to this:
* Top-Heading with process indicator [0/2]
:PROPERTIES:
:TRIGGER: 2017-12-03-target(TODO)
:END:
** TODO Here I invoke org-todo to DONE
** This should be changed to TODO
:PROPERTIES:
:ID: 2017-12-03-target
:END:
... this is also working. So the update of the process indicator
causes the wrong property drawer to be parsed for the relevant
TRIGGER property.
Contrary to my previous assumption, this is issue is *not* related
to big and small files. This is purely related to the existing or
missing process indicator of the upper-level heading.
I guess I have found the origin of the bug.
Can you please do me the favor and fix it for me. I feel
extraordinary proud of me having dig into elisp (which I don't know
how to code mostly) and found the bug ;-)
However, I can't fix it on my own :-(
Why did nobody tell me about org-edna yet? ;-)