585624 - Move to ... again not functional

Status: RESOLVED DUPLICATE of bug 574351

(Thunderbird :: Folder and Message Lists, defect)

Description

[ptyler]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2

If you move a message from your Inbox to another folder, then try to move another Inbox message to the same folder using the right-click menu option "Move to ... again" the menu option is disabled.

There are a couple of similar-sounding bugs and last week I entered comments on those, but since those were closed or assumed fixed and I never heard any feedback I'm entering this as a new bug.

Reproducible: Always

Steps to Reproduce:
1. Drag a message from the Inbox to another folder
2. Pick another message in the Inbox
3. Right click on the message
4. Choose "Move to ... again" option
5. See the option is disabled
Actual Results:  
Option is disabled and cannot be used.

Expected Results:  
The software should have allowed me to move the second message to the same folder as the first message.

This is functionality I have become accustomed to in earlier versions of Tbird, and I rely on it for Inbox maintenance. Sure I can workaround it by manually moving every message myself. But with the volume of email traffic I deal with on a daily basis, this is somewhat inconvenient. If someone could look at this and confirm the behavior, I'd appreciate it. Thanks....

Comment 1

[Joe Sabash [:JoeS1]]

WFM using:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9pre) Gecko/20100802 Lanikai/3.1.2pre ID:20100802010142

Tested with a pop3 inbox, no IMAP here.

Comment 2

[Wayne Mery (:wsmwk)]

(In reply to comment #0)
> If you move a message from your Inbox to another folder, then try to move
> another Inbox message to the same folder using the right-click menu option
> "Move to ... again" the menu option is disabled.
> 
> There are a couple of similar-sounding bugs and last week I entered comments on
> those, but since those were closed or assumed fixed and I never heard any
> feedback I'm entering this as a new bug.
 
I see your comment in only one bug, the fixed bug 432799, and as you surmised it's not unusual for comments in fixed bugs to not get much attention.

You're right it is nasty when it doesn't work. But I don't understand why you filed a new bug if bug 574351 so closely matches your description. ??

Comment 3

[ptyler]

You're right about bug 574351. That does sound like the same problem. Somehow I did not find it when searching for related bugs. This bug can be closed.