432710 - (tb-tagsmeta) [Meta] Thunderbird Tag Bugs Tracker

Status: NEW

(Thunderbird :: General, defect)

Description

[Andrew Sutherland [:asuth] (he/him)]

I've attempted to categorize and summarize the bugs briefly.  I've also attempted to deal with obvious dupes directly, but have left some potential dupes, especially in cases where people went to the effort to provide IMAP traces.  Feel free to use this as a basis for dupe-ing, and to add/remove bugs to this tracker as appropriate.  I'm sure I didn't get them all.

=== Issues
-- tag loss
bug 378973 - copying IMAP messages to local loses tags
bug 392704 - rebuild index loses tags
bug 392510 - rebuild index wipes tags when IMAP doesn't support them
bug 370440 - tags lost on IMAP messages with attachments

-- filters and tag loss/tags don't stick
bug 254589 - filters that move IMAP message across accounts don't set tags
bug 360079 - using filters to move messages from IMAP to local loses tags
bug 369745 - mail filters which apply tags and move messages sometimes lose tags
bug 380282 - tag action does not work on incoming messages (same with add star)

-- tag changes don't stick (completely)
bug 343874 - tag changes don't stick
bug 350126 - tags migrated from labels don't stick (could perhaps be (fixed) bug 348752?)
bug 383308 - removing tag doesn't remove label (tag migration issue) [good details]
bug 355205 - tags don't stay removed
bug 368210 - can't remove tags (could be a dupe)
bug 349496 - tag removal doesn't stick when using 2 clients (could be a dupe and not 2-client-specific)
bug 392371 - new tag reverts to deleted default tag
bug 376895 - only the last tag of two applied tags sticks

-- offline and tags that don't stick
bug 141606 - labels applied when offline not applied to online
bug 381324 - tags added in offline mode don't (always) stick

-- tag overflow/too many tags issues
bug 380598 - compact folder duplicates overflowed tags
bug 377791 - gives up on all IMAP tags once max keywords reached

-- mirage tags
bug 392520 - messages once labeled (and then unlabeled) look tagged, but aren't

-- IMAP related, no tag loss
bug 378883 - tag search fails on IMAP servers without keywords/keyword limit exceeded
bug 344450 - tags don't automatically work across profiles (IMAP)
bug 347263 - undo-ing deletion of a tagged IMAP message on a server without keyword support does not restore the tag
bug 431466 - tagging in IMAP folder breaks connection [probably IMAP server's fault]

-- UI bugs
bug 395495 - message windows opened from saved searches have no tags in tag menus
bug 302609 - search messages results lacks context menu
bug 398164 - tag temporarily appears on wrong message
bug 385032 - sort by tags not correct
bug 397838 - tag button shrinks in its disabled state
bug 430181 - deleting tagged messages in "grouped by sort" display results in displayed duplicates
bug 392637 - incoming messages with filter-added stars/tags cause "new mail" lingering indicators

-- misc
bug 270068 - X-Mozilla-Keys header not removed from forwarded mail

=== Enhancements
-- Filter enhancements
bug 397009 - Add untag filter action
bug 217034 - Restore capability Label/Tag as filter criterion
bug 353036 - Support "Label is None"/"No Tag" in custom views (correctly)

-- UI enhancements
bug 386707 - warn when saved search is mooted by removal of tag it depends on
bug 348128 - hierarchical tags
bug 370076 - create/apply tags using the keyboard
bug 370260 - add tags (before sending) in compose window
bug 341770 - support background colors for labels (with really pretty example link)
bug 379928 - add cross-account virtual folders based on tags
bug 379912 - add mail status flag/state
bug 395985 - ability to specify multiple tags as view criteria
bug 425359 - create a virtual folder the first time a user stars/tags a message

-- Unlikely enhancements
bug 391442 - automatically share/propagate tags among multiple users of an IMAP store

-- Ill-defined enhancement requests
bug 426134 - tag-prioritization deteriorates readability

Comment 1

[ovidiu]

Should add bug 363473 to UI enh

Comment 2

[Florian]

Please add:
https://bugzilla.mozilla.org/show_bug.cgi?id=433175

Comment 3

[Dan Mosedale (:dmosedale, :dmose)]

Added bugs mentioned in comments 1 and 2.

Comment 4

[ovidiu]

May be interesting to consider bug 435926. Today is about 2 issues that should fall under 2 specific bugs.
-resetting the default 1-5 tags (if deleted them or all tags ..)
-loosing color or alike in tags on imap (may be like some above ..)
I'll try help reporter to separate those and make sane bugs out of them and add them here after ..

Comment 5

[Thomas D. (:thomas8)]

Bug 440368 - tags not alphabetically sorted in if I rename the tag (referring to the sort order of the tag list in "Message > Tag" and "Tools > Options > Display > Tags")

The above bug should be confirmed and added to "Depends on" of this tracker Bug 432710. I think it might be a good idea to have a new category "Tag sorting bugs" (see below), otherwise  under "issues" or "UI bugs". Looks like tags are very hard to sort out... Sorting of various sorts has been reported "broken"
- when you rename tags in the settings tag list (bug 440368)
- when you apply tags to a mail (Bug 455478, incl. some discussion on the technical aspects and how tags /should/ be sorted),
- and remove tags from a mail (Bug 385032)... 
Bug 436017 concludes that "Thunderbird should sort by tags in a more meaningful way"... but the discussion about what "meaningful" means is still going on.

Out of these, please add Bug 455478 and Bug 436017 to "Depends on" of this tracker Bug 432710, ideally under the suggested new category "Tag sorting bugs", otherwise under "issues" / "UI bugs".

Comment 6

[Thomas D. (:thomas8)]

Bug 368084 ~ Unable to change number shortcut key association of tags
--> should be added to this tracker's "Dependent on"

Bug 368084, Comment #2, adding/renaming tags messes up shortcut key association due to wrong design of pref pane (alphabetical auto-sorting causes unwanted shortcut key assignment) - (should this be filed as a separate bug?)

Comment 7

[Karsten Düsterloh]

> Bug 368084 ~ Unable to change number shortcut key association of tags

Added.

> Bug 368084, Comment #2, adding/renaming tags messes up shortcut key association
> due to wrong design of pref pane (alphabetical auto-sorting causes unwanted
> shortcut key assignment) - (should this be filed as a separate bug?)

If bug 368084 would be fixed, allowing for custom shortcut assignments, your remaining claim would be fixed also, so I don't think another bug is needed.

Comment 9

[Thomas D. (:thomas8)]

Plenty of candidates for bugs to be added to this meta bug (currently 158, including some erratic matches):

bmo quicksearch for
:thun,mail su:tag -su:html,percentage,stage,

https://bugzilla.mozilla.org/buglist.cgi?quicksearch=%3Athun%2Cmail%20su%3Atag%20-su%3Ahtml%2Cpercentage%2Cstage%2C;list_id=5264426

Comment 10

[Thomas D. (:thomas8)]

In view of comment 9, I wonder if we could split this rather large cesspool Meta bug into two:

1) tbtagsuxtracker: with focus on improving the UX (mostly RFEs, usability/design bugs allowed, but no strictly technical bugs)

2) tb-tagsfailtracker: (only technical bugs where things are really broken, no RFEs)

Example for 1):
Bug 520560 - Implement a label / tagging system like Gmail - with new features

Example for 2):
bug 791925 - Tags are lost by deletion of .msf, if tags are added at IMAP folder and mail is moved from IMAP folder to local mail folder, unless overflow of X-Mozilla-Keys: happens and Compact writes all tags in expanded X-Mozilla-Keys: header.

We'll certainly have edge cases and a bit of fuziness especially for 1), but IMO this model of focussing on "UX bugs" (mostly RFEs) seperately worked fairly well for attachuxtracker Bug 579473.

The obvious advantage is that both meta bugs will be more valuable as they contain less dependants and are more focused on UX vs. Technical issues.
On the other hand, you'll have to think a little bit harder before adding to one of the two metas...

(I'm deliberately using different Alias syntax with and without hyphen so that when you add the Alias into "Blocks" field of existing bugs, typing only three letters suffices to trigger your browsers input field autocompletion, something I successfully used for tb-keyboard-tracker vs. tbkbd-doc-tracker).

Opinions?

Comment 11

[Wayne Mery (:wsmwk)]

(In reply to Thomas D. from comment #10)
> In view of comment 9, I wonder if we could split this rather large cesspool
> Meta bug into two:
> 
> 1) tbtagsuxtracker: with focus on improving the UX (mostly RFEs,
> usability/design bugs allowed, but no strictly technical bugs)
> 
> 2) tb-tagsfailtracker: (only technical bugs where things are really broken,
> no RFEs)
> 
> Example for 1):
> Bug 520560 - Implement a label / tagging system like Gmail - with new
> features
> 
> Example for 2):
> bug 791925 - Tags are lost by deletion of .msf, if tags are added at IMAP
> folder and mail is moved from IMAP folder to local mail folder, unless
> overflow of X-Mozilla-Keys: happens and Compact writes all tags in expanded
> X-Mozilla-Keys: header.
> 
> We'll certainly have edge cases and a bit of fuziness especially for 1), but
> IMO this model of focussing on "UX bugs" (mostly RFEs) seperately worked
> fairly well for attachuxtracker Bug 579473.
> 
> The obvious advantage is that both meta bugs will be more valuable as they
> contain less dependants and are more focused on UX vs. Technical issues.
> On the other hand, you'll have to think a little bit harder before adding to
> one of the two metas...
> 
> (I'm deliberately using different Alias syntax with and without hyphen so
> that when you add the Alias into "Blocks" field of existing bugs, typing
> only three letters suffices to trigger your browsers input field
> autocompletion, something I successfully used for tb-keyboard-tracker vs.
> tbkbd-doc-tracker).
> 
> Opinions?

I think this approach helped in the case of filters. And so I am in favor, especially if it helps get bugs fixed.

Until this is done you can get a horrible rough approximation (but only of the bugs linked as of today) by sorting the following query by component (N.B. you must have the component column in your query display) - https://bugzilla.mozilla.org/buglist.cgi?bug_id=397838%2C547461%2C289411%2C536946%2C363473%2C380282%2C379928%2C425359%2C455478%2C370076%2C392510%2C270068%2C378973%2C683809%2C721901%2C440368%2C392637%2C349496%2C355205%2C426134%2C368210%2C472518%2C764735%2C471399%2C386707%2C369745%2C474569%2C381961%2C352651%2C360079%2C590075%2C347957%2C398164%2C177032%2C392520%2C766076%2C378883%2C456169%2C430181%2C368084%2C376895%2C385032%2C448289%2C760856%2C383308%2C439132%2C347263%2C431466%2C693204%2C343874%2C382117%2C254589%2C348128%2C486973%2C217034%2C234935%2C344450%2C395495%2C341770%2C352869%2C370260%2C439548%2C141606%2C380598%2C350126%2C528034%2C450246%2C568090%2C397009%2C435866%2C367011%2C379912%2C392704%2C377791%2C436017%2C328648%2C765637%2C433175%2C381324%2C151638%2C439835%2C395985%2C353036%2C551816%2C781466%2C533337%2C370440%2C135472%2C119162%2C392371%2C391442%2C364348%2C520560%2C302609&list_id=9782164