From: Julius Dittmar <Julius.Dittmar@gmx.de> To: firstname.lastname@example.org Subject: Re: Archiving repeated tasks under corresponding date tree for each repeated item Date: Mon, 2 Nov 2020 15:18:57 +0100 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <CAF4Fj9jK5fDsTgbQBLdY=LVPjX+2yKWNQHYtCJh6ccmuAnMivw@mail.gmail.com> Hi Gerardo, I am by far no expert, but I think with the kind of setup you currently use your goal cannot be reached: The repeating task you use is one single task, and it will be archived as that one single task. There's a different way to approach repeating tasks though that might meet your requirements: Copying that task for each repeat. There's a command (org-clone-subtree-with-time-shift) that lets you copy a task easily. With that you have different tasks that can be archived separately. I did never use this approach myself though. Perhaps that helps, Julius Dittmar Am 29.10.20 um 08:01 schrieb Gerardo Moro: > When I archive a repeated task (let's say, a learning project of 15 minutes > every Wednesday day for 2 months), the task gets archived in a date tree > all under the day it was closed (cancelled) as a whole. This means that all > the LOGGED individual instances of repetition are archived on the day the > project got completed. It would be great if each of these individual "task > happenings" were archived under the date and time they were completed > individually, and not just all as one block. This way I could get weekly > reviews that take those into account.
next prev parent reply other threads:[~2020-11-02 14:22 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <CAF4Fj9hjjQ98gGe7hRp0tU4qPtZ-ekUUpO9niNpJ+s31g2buOA@mail.gmail.com> 2020-10-24 4:06 ` Gerardo Moro 2020-10-29 7:01 ` Gerardo Moro 2020-11-02 14:18 ` Julius Dittmar [this message] 2020-11-03 5:52 ` Ihor Radchenko 2020-11-12 7:59 ` Gerardo Moro 2020-11-12 10:27 ` Ihor Radchenko 2020-11-16 15:21 ` Gerardo Moro 2020-11-17 8:58 ` Gerardo Moro 2020-11-17 9:31 ` Ihor Radchenko 2020-11-17 12:00 ` Gerardo Moro 2020-11-17 12:31 ` Ihor Radchenko 2020-11-17 12:57 ` Gerardo Moro 2020-11-17 13:12 ` Ihor Radchenko 2020-11-17 15:35 ` Gerardo Moro 2020-11-17 15:59 ` Ihor Radchenko 2020-11-17 16:15 ` Gerardo Moro 2020-11-18 5:36 ` Ihor Radchenko 2020-11-18 8:35 ` Gerardo Moro
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Archiving repeated tasks under corresponding date tree for each repeated item' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).