I am very often using Thunderbird labels that allow me to decide whether a particular message needs any action or status.
Those labels are strictly defined within client settings.
Issue is, when having a few mailboxes configured, the labels are the same for all of them.
Also, labels available on one client are not necessarly available on the other client, especially when they have been manually configured and evolved over time.
Thus, issue #1 is no way to import and export labels, besides copying and pasting part of prefs.js - import and export would be awesome.
issue #2 is the labels are strictly defined for the whole client, not for mailbox. Having them configurable for each mailbox would be a huge advantage.
issue #3 is: all the different labels used on other TB clients may not be visible on my client, just because they are not defined, although they are stored as IMAP flags nevertheless. Say I have label keys manually configured as "$label1" through "$label9" and the other client has auto configured key as "client_scomplaint" for label #4. My "$label4" is completely different than "client_scomplaint" BUT in my opinion there should be an option to at least preview others' labels stored in IMAP flags and add them manually as additional labels (not shortcuted 1 through 9) in my client (auto collecting may be an issue over time).
issue #4 is: there is no way to know who set or disabled a label for a message. At least knowing who set particular label would be awesome. This could be done either as key extension or some additional flag, adding a profile name in form of a comment.
issue #5 is: labels may diverge over time. Modifying a label in a client may or may not (based on unknown factors) change its key. My guess is the key is created when creating a label, and then stays unmodified when modifying the label. Even if the clients were configured by pasting the same keys and values for labels in prefs.js, they may diverge over time, when one client is reconfigured manually and the other is not, leading to confusion in what actions are expected for a particular message, just because the label key is the same but the values (actions) are now different. An option (a checkbox) to update a key automatically would be the best way out.
issue #5 may be shortcuts for labels. While 1 through 9 is enough for most cases, sometimes another layer would be of help. It'd be a blessing if there was an option to configure custom shortcuts for labels, that might be launched from a Stream deck type of keyboard.
