GNOME Bugzilla – Bug 230978
Inconsistency between "Mark as Important" and "Label -> Important"
Last modified: 2016-04-08 11:34:46 UTC
Please fill in this template when reporting a bug, unless you know what you are doing. Description of Problem: Things which may have been overlooked in the implementation of labels: (1) The label option is not avaliable from any menu; it is only avaliable by right clicking. (2) The avaliable "actions" for filtering do not include the option to label . Although they permit color-coding, this is separate from Labeling. i.e. the filter added color can't be removed by selecting "label -> none". (3) Labeling something as "important" doesn't toggle the important flag; indeed, the two colors are inconsistent. A wonderful new feature, though, especially if it can be connected to filtering.
Also, Evo should support adding Label as a column in the mail view and we should be able to sort based on label.
first item is the same as bug 269852
still valid in 2.5.5
Bumping version to a stable release.
(In reply to comment #1) > Also, Evo should support adding Label as a column in the mail view and > we should be able to sort based on label. This is present in 2.26 (and probably already in earlier versions, haven't investigated).
In 2.29.2 labels can be used as filters in search panels and are optionally shown as column in the mail view. It persists the inconsistency between "Mark as Important" and "Label -> Important": how those two flags are intended to be used? Which is their relative aim? Are them related in some way?
The two options are fully independent, it's only a coincidence that the name sounds similar. The 'Mark as Important' is a (bool) flag on the message, while the 'Label -> Important' is a tag on a message, which is, in case of IMAP, a user-defined text tag which may or may not be stored on the server. The coloring and labeling a message are also two independent things. It's the label which also covers a color, not the message has set the color too. As all the other brought parts are already covered in the current stable version (3.20.0 as of today), I'm closing this.