Hi! When an entry got processed by org-clone-subtree-with-time-shift, its :CREATED: property gets shifted too:
#+begin_example * <2011-10-04 Tue> test SCHEDULED: <2011-10-05 Wed> :PROPERTIES: :CREATED: <2011-10-04 Tue 17:27> :END: * <2011-10-11 Tue> test SCHEDULED: <2011-10-12 Wed> :PROPERTIES: :CREATED: <2011-10-11 Tue 17:27> :END: #+end_example Although this *might* be on purpose, I strongly argue to stop this behaviour because of: * the entry is not really created in the future. It is created either at the original :CREATED: timestamp _or_ it is created at the timestamp when org-clone-subtree-with-time-shift is executed. * the user gets heavily irritated when the generated entries keep popping up on future days. I suggest that at least for :CREATED: properties, the time stamp does not get changed by org-clone-subtree-with-time-shift. -- Karl Voit
