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 235160 - possibility to set filter to a relative future date
possibility to set filter to a relative future date
Status: RESOLVED DUPLICATE of bug 211058
Product: evolution
Classification: Applications
Component: Mailer
1.5.x (obsolete)
Other All
: Normal enhancement
: Future
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2002-12-05 19:12 UTC by steveNOSPAM
Modified: 2004-08-28 02:34 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description steveNOSPAM 2002-12-05 19:12:07 UTC 
Package: Evolution
Priority: Wishlist
Version: 1.2.0
Synopsis: filter enhancement request
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer

Description:
Description of Problem:

When I set a filter, I want to set a relative date.  However, the only
direction I can go is back ("... ago"). 

When I look in my trash, the top 10 files are often... um.... auful
porn.  They're at the top when I sort by date.  Their dates are Dec 30
2014, Dec 30 2020, etc...

Steps to reproduce the problem:
1. NA 
2. 
3. 

Actual Results:
NA

Expected Results:
NA

How often does this happen?
NA

Additional Information:
NA



Unknown reporter: steveNOSPAM@SPAMmeNOTcontentwatch.com, changed to bugbuddy-import@ximian.com.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Comment 1 Jeffrey Stedfast 2002-12-05 21:36:39 UTC 
this might be a duplicate
Comment 2 André Klapper 2004-03-15 12:58:52 UTC 
still only past possible in evo1.4.6, no future available.
Comment 3 André Klapper 2004-06-24 19:05:59 UTC 
still missing in evolution1.5-1.5.9.0.200406211628-0.snap.ximian.8.1.
Comment 4 André Klapper 2004-08-28 02:34:06 UTC 

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