Bug 293655 - implement filter bar similar like in Thunderbird
Summary: implement filter bar similar like in Thunderbird
Status: REPORTED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 1.6.6
Platform: Unlisted Binaries Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-08 16:58 UTC by m.wege
Modified: 2021-03-09 04:10 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot showing Thunderbird (9.55 KB, image/png)
2012-02-08 17:08 UTC, m.wege
Details

Note You need to log in before you can comment on or make changes to this bug.
Description m.wege 2012-02-08 16:58:05 UTC
Version:           1.6.6 (using KDE 4.8.0) 
OS:                Linux

I would like to see the filterbar in the message list implemented in a similar
way like in thunderbird. I will attach a screenshot of their filterbar. Their
way of filterbar has following advantages:
- filter criteria (unreadsare accessible faster since there is no dropdown menu
necessary.
- filter criteria can be combined.
- There is a "sticky" item, which allows to choose if the filter should remain
in effect, if you change the mail folder.
Furtheremore I would like to suggest to implement an additional filter critera:
Filter by date range (from/(to)).
I filed this wish item also with Kmail

Reproducible: Always

Steps to Reproduce:
See above

Actual Results:  
See above

Expected Results:  
See above

See above
Comment 1 m.wege 2012-02-08 17:08:55 UTC
Created attachment 68625 [details]
Screenshot showing Thunderbird
Comment 2 Laurent Montel 2012-02-08 17:17:55 UTC
"There is a "sticky" item, which allows to choose if the filter should remain
in effect, if you change the mail folder." already implemented in 4.9
Comment 3 Justin Zobel 2021-03-09 04:10:55 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.