After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 546244 - 'Mark as Uninportant' does not equal 'Unmark as Important'
'Mark as Uninportant' does not equal 'Unmark as Important'
Status: RESOLVED DUPLICATE of bug 301404
Product: evolution
Classification: Applications
Component: Mailer
2.12.x (obsolete)
Other Linux
: Normal trivial
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-08-04 14:07 UTC by Werner Heijstek
Modified: 2009-02-12 04:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Werner Heijstek 2008-08-04 14:07:17 UTC 
A message can be marked 'important' by selecting 'Mark as Important' from the menu that appears after right clicking (default behaviour) any mail message. A message that has been marked as 'important' can be unmarked as important. 

The option that the little message-specific menu offers for this action is labeled 'Mark as unimportant' implying that 'unimportant' is a new (or different) which is not true. The 'important' flag is merely removed. This means that the option to remove the 'important' flag should be named something like 'Unmark as important' or 'Remove important flag' instead of 'Mark as unimportant'.
Comment 1 Matthew Barnes 2008-08-04 15:13:46 UTC 
My guess is it was worded that way for consistency with "Mark as Unread" and "Mark as Not Junk"; for you could make the same argument for those as well: "Unmark as Read" and "Unmark as Junk", which sound awkward.

I'm not necessarily disagreeing with you, but if we change one we need to change all three, and I'm not sure that's worth it.

Note, you can also toggle the "Important" flag by just clicking the icon directly (or where it would appear).
Comment 2 Matthew Barnes 2009-02-12 04:44:27 UTC 

*** This bug has been marked as a duplicate of 301404 ***