Closed Bug 392371 Opened 17 years ago Closed 15 years ago

New tag is reverting to another default tag after it's been assigned to an email

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: clt, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: closeme 2009-08-09)

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.0.3705; .NET CLR 1.1.4322; Media Center PC 4.0; .NET CLR 2.0.50727; InfoPath.1) Build Identifier: Thunderbird Portable, 2.0 I created some new tags. I deleted some of the default tags because I wasn't going to use them anyway. Specific example is when I assign the tag "Customer Service" to various emails, they revert to "Important", which was a default/original tag. So, I deleted "Important" in the Options area, but it continues to do the same. Reproducible: Always Steps to Reproduce: 1. Assign Tag to emails of "Customer Service" which was a new tag I created within the Tools/Options folder 2. Reverts to "Important" tag on its own 3. Deleted "Important" tag assuming that would take care of it 4. Continues to do the same thing 5. Other tags, newly created, seem to work fine so far 3. Actual Results: see above Expected Results: see above The tag "Customer Service" should remain applied to emails I have selected and applied it to.
What type of mail folder are you using when this happens? (IMAP, Local Folders/POP3). Did you use a version of Thunderbird earlier than 2.0 previously on the mail folder (namely 1.5 or earlier)? If so, did you ever use Thunderbird's "Label" functionality to apply the Important label to the message?
Reporter any reply to comment #1?
Whiteboard: closeme-08/09/2009
Whiteboard: closeme-08/09/2009 → closeme 2009-08-09
Closing Incomplete for lack of answers. Feel free to reopen if you can provide more information.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.