> it seems to me that it's more 'depend' in the sense of 'this task has > to be done for this other task to be doable'.
IIRC, the TRIGGER property in org-depend.el allows you to change the state of another tree when the current one is marked done. I imagine you could use it to have a clone task in another tree that is TRIGGERed to change to done when the other is. Example * Some tree ** TODO Update CV :PROPERTIES: :TRIGGER: cv-clone(DONE) :END: * Some other tree ** TODO Update CV clone :PROPERTIES: :ID: cv-clone :END:
