Closed Bug 413918 Opened 17 years ago Closed 17 years ago

Users must use Tools Menu to delete entire Junk Folder contents

Categories

(Thunderbird :: Mail Window Front End, enhancement)

x86
Windows XP
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 189911

People

(Reporter: hantwister, Unassigned)

Details

User-Agent:       Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; InfoPath.1)
Build Identifier: 20071031

Currently, if users want to delete the contents of the Trash Folder, they can simply right click the Trash Folder and select Empty Trash. In comparison, to delete the contents of the Junk Folder, a user must click the Tools Menu, then select Delete Mail Marked as Junk in Folder. Although I am not suggesting that this be removed (sometimes useful after marking items as junk in Inbox then deleting all the aforementioned items), it seems unintuitive when a user is simply trying to delete the contents of the Junk Folder, just as they would try to delete the contents of the Trash Folder.

This is an enhancement request - I think it would be easier for some users if the Junk Folder had some way to empty it's contents via it's Context Menu.

Thanks,
-HN

Reproducible: Always

Steps to Reproduce:
1. Receive e-mail Thunderbird would mark as junk.
2. Allow Thunderbird to process the incoming messages, and move the junk items to the Junk Folder.
3. Attempt to delete the contents of the Junk Folder in a similar manner to how one might delete the contents of the Trash Folder.
Actual Results:  
The user either remembers from past experience that he/she must use the option to delete junk in the Tools Menu, looks around for such an option, or resorts to deleting items one by one.

Expected Results:  
The user would have been able to click and use an option to delete the contents of the Junk Folder using the Junk Folder's Context Menu.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.