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 714795 - Option to only display unread messages
Option to only display unread messages
Status: RESOLVED DUPLICATE of bug 714983
Product: geary
Classification: Other
Component: client
master
Other All
: High normal
: ---
Assigned To: Geary Maintainers
Geary Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-03-25 06:13 UTC by Jim Nelson
Modified: 2014-02-12 23:44 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Charles Lindsay 2013-11-21 23:11:25 UTC


---- Reported by jim@yorba.org 2013-03-25 11:13:00 -0700 ----

Original Redmine bug id: 6663
Original URL: http://redmine.yorba.org/issues/6663
Searchable id: yorba-bug-6663
Original author: Jim Nelson
Original description:

One of our IndieGoGo contributors asked for an option to display only unread
messages, as a way of filtering out email. This option should be easily
switched on and off (perhaps on the toolbar) to make it easy to flip back and
forth.



---- Additional Comments From geary-maint@gnome.bugs 2013-04-03 18:22:00 -0700 ----

### History

####

#1

Updated by Jim Nelson 8 months ago

  * **Target version** changed from _0.4.0_ to _0.5.0_



--- Bug imported by chaz@yorba.org 2013-11-21 23:11 UTC  ---

This bug was previously known as _bug_ 6663 at http://redmine.yorba.org/show_bug.cgi?id=6663

Unknown milestone "unknown in product geary. 
   Setting to default milestone for this product, "---".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Resolution set on an open status.
   Dropping resolution 

Comment 1 Michael Gratton 2014-02-12 23:41:15 UTC
Duplicate of #714983?
Comment 2 Jim Nelson 2014-02-12 23:44:27 UTC
Yes!  Thank you.

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