Closed Bug 349396 Opened 19 years ago Closed 17 years ago

Copy news posting to local folders loses Tag information

Categories

(MailNews Core :: Backend, defect)

1.8 Branch
x86
All
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: bugzilla.alex, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060808 SeaMonkey/1.5a Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060808 SeaMonkey/1.5a If you copy a news posting with a Tag like "personal" or "to do" in a local folder so you lost this Tag at the new message. If the Tag one of the old Labels (set with seamonkey 1.0) so the copy doesn't left the Tag. Reproducible: Always Steps to Reproduce: 1. set a Tag at a news posting 2. copy the news posting in a local folder 3. the copy of the posting has no Tag
Also happens in SeaMonkey 1.1a Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1b1) Gecko/20060803 SeaMonkey/1.1a Mnenhy/0.7.4.10002
Confirmed with TB 2a1-0818, Win2K.
Status: UNCONFIRMED → NEW
Component: MailNews: Main Mail Window → MailNews: Backend
Ever confirmed: true
OS: Windows XP → Windows 2000
Product: Mozilla Application Suite → Core
Summary: duplicate a news postings in a local folder reset the Tag → Copy news posting to local folders loses Tag information
Version: unspecified → 1.8 Branch
Linux too.
OS: Windows 2000 → All
do you still see this? drag tagged message WFM on trunk version 3.0a1pre (2008011304). similar to bug 384853.
Assignee: mail → nobody
QA Contact: backend
Product: Core → MailNews Core
Dragging a msg to local keeps the tag now on trunk. Copy doesn't do anything though :( Filed bug 451971.
I couldn't reproduce the bug now with a current SM 2.0 build.
->WFM on thunderbird linux/trunk too.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
v. with U; Windows NT 6.0; en-US; rv:1.9.1b3pre) Gecko/20081209 Shredder/3.0b2pre - so apparently working for a long time.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.