After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 732331 - deleting drafts and trashed messages is confusing
deleting drafts and trashed messages is confusing
Status: RESOLVED DUPLICATE of bug 794499
Product: geary
Classification: Other
Component: ux
master
Other Linux
: High normal
: ---
Assigned To: Geary Maintainers
Geary Maintainers
Depends on: 726100
Blocks:
 
 
Reported: 2014-06-27 10:56 UTC by justcomplaining
Modified: 2018-03-19 21:10 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description justcomplaining 2014-06-27 10:56:07 UTC 
Drafts are shown as a part of their related conversation, wich makes it impossible to select it individually. If the whole conversation is selected and deleted, the draft is the only email that actually gets removed, which is the action I would normally want to trigger, but it is not apparent, that that's the case. Additionally, the dialogue that asks for confirmation is asking for "messages" in plural, wich is not correct and misleading.

The same behavior is shown in trash folders.

Clarification would be great :)

A big part of the solution would be solving bug 726100 / bug 714674

The tooltip of the "trash" button should be "Trash draft" in draft-folders and "Delete trashed messages" in trash-folders. Or something like this...
Comment 1 Federico Bruni 2017-12-19 23:22:17 UTC 
Yes, bug 726100 would solve the big problem.

The other problem you mention is ticketed here:
Bug 730607 - "Close open draft messages?" dialog should be singular for single inline composer

See also Bug 730486 - Show drafts as inline composer windows when viewing conversations
Comment 2 Michael Gratton 2018-03-19 21:10:30 UTC 
All those are definitely applicable, but I think both Drafts and Outbox need special handling. I've filed Bug 794499 to cover this, so I'm going to mark this as a duplicate of that.

*** This bug has been marked as a duplicate of bug 794499 ***