Closed
Bug 246436
Opened 20 years ago
Closed 20 years ago
More labels
Categories
(Thunderbird :: General, enhancement)
Thunderbird
General
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 114656
Thunderbird 11.0
People
(Reporter: wcc, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040605 Firefox/0.8 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040605 Firefox/0.8 It would be very useful to have more than just 5 mail "labels". I am a developer, and I get lots of project-related mail for one of the larger projects I work on. For patches, I like to be able to label patches in the "Patches" folder as either "Applied", "Pending Discussion", or "Will Not Be Applied". For CVS commit logs, I like to be able to label them as "Reviewed" (Quality Control....), or "Reverted" if they were later reverted, to make going through old commit logs faster. For bugs, I like to be able to mark them as "Fixed" or "Important", etc. I have tons of uses for these labels.. there should be an option to allow for more of them. Reproducible: Always Steps to Reproduce: Not Applicable. Actual Results: Not Applicable. Expected Results: Not Applicable. Not Applicable.
Assignee | ||
Updated•20 years ago
|
Whiteboard: dupme
Target Milestone: --- → After Thunderbird 1.
Comment 1•20 years ago
|
||
I agree, more than 5 labels would be good and AFAIK also easy to implement. The problem is, that there's only room for at most 7 labels in the X-Mozilla-Status2 header: 1 0x02000000 2 0x04000000 3 0x06000000 4 0x08000000 5 0x0A000000 6 0x0C000000 7 0x0E000000 see http://lxr.mozilla.org/seamonkey/source/mailnews/base/public/nsMsgMessageFlags.h#126
OS: Linux → All
Hardware: PC → All
Comment 2•20 years ago
|
||
Oops dupe. *** This bug has been marked as a duplicate of 114656 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Comment 3•14 years ago
|
||
Cleanup *dupeme* whiteboard flag from bugs that are marked as Resolved Duplicate!
Whiteboard: dupme
You need to log in
before you can comment on or make changes to this bug.
Description
•