Task-By threads, Reminders, New tasks made of replies, and the color tag 'Later'

This email brings to your attention four topics
Task-By threads: how to keep all emails of the thread stuck together when moving the entire thread from one IMAP folder to another?
Reminders: shall the reminder emails of the thread be colored or moved with the thread?
New tasks made of replies: how to create the next new task, when I wish to create it in reply to a Done-By email?
The colored tag 'Later': what is the meaning of the new colored tag 'Later'?

Task-By threads:

This email contains at the bottom an example of a Done-By of Ghislain, which was moved to the 'ok' folder of the project, but the main Task-By was left in the project. This is obviously an error. When the task is finished, not only your Done-By must be moved into the 'ok' folder, but also the task itself must be moved into the 'ok' folder. Since your Done-By is a reply to the Task-By, these two emails will be shown stuck together. You must always use the Thunderbird in thread view mode to show the replies stuck to the original email. When the task is complete all emails of the Task-By thread must be moved into 'ok' folder. The task-by and the done-by emails must be uncolored first (by pressing '0') and then colored by 'work' tag in orange (by pressing '2'). The thread may have other emails (neither a Task-By nor a Done-By) such as reminders and remarks. Normally the thread must consist of only two emails (the Task-By and Done-By). Other un-prefixed emails indicate on delays or errors. The remarks and reminders (usually sent only by the author of the task) are not colored and are not prefixed by Done-By or Task-By. But similarly to Done-By, they must voyage with the task when migrating, meaning that when you move the Task-By with the Done-By to 'ok' you must move also all other emails of the thread (if any). When you move the emails of the thread you must be careful. Always the thread's higher hierarchy parent email must be moved first, because in the new folder the parent email must appear (i.e. must be saved) before the child email. There is an internal order which we do not see. This is the order in which the emails are saved. The parent email must be saved before the child email. Therefore first you must move the Task-By, then the other sub-emails of the thread. If you do the opposite the emails will not stick to Task-By as the main Task-By is moved afterwards. If you did such an error, move back the sub-emails into the main folder, and then move them again to the 'ok' sub-folder. By doing this you will re-save the child email after the parent email and if they were supposed to join, they will re-stick again as they were stuck in their original IMAP folder.

Here what you must recall from the above said.

o Before coloring to orange (the tag 'work' corresponding to key '2'), you must un-color emails by pressing '0'. If you do not do this, you will see the orange color, but the email will be still tagged also in blue causing errors in searches.

o The Thunderbird must be ALWAYS used in thread-view mode ONLY. This is applicable to all folders, to project folders and especially to 'ok' folders. If the project folder is viewed in non-thread view and it contains reminders (uncolored and un-prefixed emails), you will not see to which task they belong and they will pollute your overall view.

o When moving threads to other folders (i.e. most of the time to 'ok' sub-folder), move them in the hierarchical order of the thread. First move the parent then the child emails of the thread. If the parent is saved in the new folder after the child, the emails will not be organized into a thread in the new 'ok' sub-folder. If you see such an error, you can correct it by moving the child back into the project folder and re-moving it again into the 'ok' folder (to enforce the saving of the child after the parent).

Reminders:
Un-colored emails can happen in projects in reply to tasks. The task's thread can contain a reminder in reply to the main task. The reminder does not have a color, neither a "Task-By" prefix. The reminder is provided in reply to a task (normally by the author of the task) and is never colored. The IMAP folder must be always viewed in thread view to see the reminders stuck with their tasks. When the task is done, the Done-By reply must be provided and only the Task-By and Done-By emails must be colored in orange (meaning 'work'). The entire thread (the task, reminders, and the done proof) must be moved into the 'ok' sub-folder. Reminders and remarks remain uncolored.

New tasks made of replies:

Often you need to create a new task immediately in reply to a Done-By of the preceding task. If you use the reply button and save your new task in the project folder, one day, when your new task is moved into 'ok' folder where the previous task already resides, the new task will stick to the first one forming a big thread (even if you was careful enough to change the subject). As we know, each task must be always at the head of its own thread and must not stick to other threads. To avoid this, and still having the comfort of replying sometimes to done proofs, the following procedure must be followed. Click on reply button in reply to the 'Done-By' (from which you want to create your next task), but do not save! Open a new virgin message window. Copy-paste from the reply window all text into the new message window (Ctrl-A, Ctrl-C, and Ctrl-V). Close the original reply window without saving it and save instead the new message window. Your new email will contain all you need to look as a reply, but it will not contain in its header (the part you do not see), i.e. the message ID of the original email. Therefore it will never stick to its original email, the day both of them will find themselves in the same IMAP folder. You obviously must take care of the Task-By prefix and of the change of the subject because Thunderbird, when merging emails into threads, relies not only to the message ID but also to the subject.

The colored tag 'Later':

This color tag is reserved for lasting messages, such as read-me, how-to, stats, and announces. For example, this message is tagged by this color (key '5').

*   *   *