Closed Bug 7557 Opened 26 years ago Closed 25 years ago

Can't Move/Copy to parent folder - no way to select it.

Categories

(MailNews Core :: Backend, defect, P2)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: laurel, Assigned: alecf)

References

Details

(Whiteboard: [PR1])

Using jun03 builds on NT4.0, Linux and Mac OS 8.51 There is no way to select a parent folder for a move or copy message destination. The menu allows selection of the subfolders, but not the parent folder. 1. POP account includes folders such as: Afolder |_ Bfolder |_ Cfolder 2. Launch to messenger, select a message in inbox. 3. Message|Move Message or Message|Copy Message and try to select Afolder as the destination. Result: You can't. The menu doesn't allow selection at the parent level. Since there is no drag and drop available or other means of getting messages into such parent folders, this is a hinderance for real mail usage.
Priority: P3 → P2
QA Contact: lchiang → laurel
Status: NEW → ASSIGNED
Target Milestone: M10
Setting to M10 with other copy stuff.
Whiteboard: [PR1]
This needs to be fixed by PR1, so I added a note in the Status Whiteboard
Assignee: putterman → alecf
Status: ASSIGNED → NEW
reassigning to alecf
Status: NEW → ASSIGNED
I've got template to do this in my tree.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
added a "File Here" menu item and a separator. RDF templates rock.
Depends on: 13880
Well, the File Here for selecting destination as a parent folder is in, but it doesn't work -- will verify when 13880 is fixed.
Using 19991003 win and 19991001 mac and linux M10 builds, this still now testable since 13880 is still not fixed.
Target Milestone: M10 → M12
Taking the liberty of moving the TFV to m12 since the bug this depends on is marked for m12. We won't be able to verify until then. Not a stopper anyway.
Status: RESOLVED → VERIFIED
Verified using 1999-10-19-08 NT 4.0, 1999-10-19-08 linux 6.0 and 1999-10-19-08 mac OS 8.5
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.