Closed Bug 425661 Opened 16 years ago Closed 16 years ago

Tag-Prioritisation (Readability). Filters do not allow to remove(!!!) tags from messages or to form free(!!!) boolean expressions or to order the tags' display priority.

Categories

(Thunderbird :: Mail Window Front End, enhancement)

x86
Windows XP
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: michel, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050702
Build Identifier: Version 2.0.0.12 (20080213).

Moin Moin.

The Tag-Prioritisation deteriorates readability by displaying always the highest prioritised tag, regardless of the context, that might not even be discerned/filtered by the message-filter-system.
Messagefilters do not allow to remove(!!!) tags from messages (attached to them by higher prioritised filters).
An alternative would be to form free(!!!) boolean expressions like:
 if (sender is "a" OR sender is "b" or recipient in "c") AND tag is not "Aldi".
But this option is disallowed due to the inability to form brackets.


Reproducible: Always

Steps to Reproduce:
1.
2.
3.


Expected Results:  
It should be possible to insert brackets (just like inserting new constraints like (sender is "a").
It would help to be able to REmove an already set tag.
It would help to be able to prioritise the tags' displaymode.
This bug is invalid because it covers three separate issues.

If you have a proposal that improves readability by replacing the tag priority mechanism, then you can certainly request it as an enhancement, if it has not been requested here already.

Filters for removing tags are: bug 397009

Boolean expressions are: bug 297852

Moin Moin.
Actually it is valid with respect to, what tagging is meant to do.
It should help in highlighting a message-box's meaning-distribution.
Discerning meaning imposes the need to place several conjunctive(!) restrictions upon the discerning algorithm.
Of course they might be applied, if the different aforementioned capabilities were implemented separately.
But, in order to help to debug them, they should somehow be linked to each other.
However, if it helps to create disparate bug-entries, be it so.
Using an inheritance-like notion, I shall be entering three new requests mentioning/referring to this very one.
They should be available under: "https://bugzilla.mozilla.org/show_bug.cgi?id=426134", "https://bugzilla.mozilla.org/show_bug.cgi?id=426135", "https://bugzilla.mozilla.org/show_bug.cgi?id=426136".
_Tschuess,
__Michael.
Closing as invalid, because of too many different issues and new bugs filed for those.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.