Closed Bug 313402 Opened 19 years ago Closed 17 years ago

After moving a filter up or down in the filter-manager, the filter should stay selected

Categories

(Thunderbird :: Mail Window Front End, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 368218

People

(Reporter: BesTo, Assigned: mscott)

Details

Message-Filters should be sorted by name:
no, they're arranged in the order that they'll execute, which is very important.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Changed summary from: Message-Filters should be sorted by name: to: After moveing an filter up or down in the filter-manager, the filter should stay selected.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Summary: Message-Filters should be sorted by name: → After moveing an filter up or down in the filter-manager, the filter should stay selected.
Summary: After moveing an filter up or down in the filter-manager, the filter should stay selected. → After moving a filter up or down in the filter-manager, the filter should stay selected
You should been abled to sort the filter only for display and search, not for the order of working. I have over 300 filters. It is nearly impossible to find the rule I want to change. To group the filters with moving (alt-u or alt-o) is a time getting action
You should been abled to sort the filter only for display and search, not for the order of working. I have over 300 filters. It is nearly impossible to find the rule I want to change. To group the filters with moving (alt-u or alt-o) is a time getting action
This has nothing to do with sorting the filters. They are sorted in the order that they work. Sorting would make the list meaningless. If you want this enhancement, please file under another bug (after searching first. ) :)
QA Contact: front-end
(In reply to comment #2) > Changed summary from: > Message-Filters should be sorted by name: > to: > After moveing an filter up or down in the filter-manager, the filter should > stay selected. > that is probably bug 368218 (recent active)
The original description of this bug (and comment 3) is a dupe of bug 256582. The new description this was renamed to (by the originator in comment 2) is a dupe of bug 36218, and that's what I'm duping this to.
Status: REOPENED → RESOLVED
Closed: 19 years ago17 years ago
Resolution: --- → DUPLICATE
(In reply to comment #7) > is a dupe of bug 36218 I cant seem to type correctly today. That should have been bug 368218. At least I got it right in the dupe field. ;^>
You need to log in before you can comment on or make changes to this bug.