Closed Bug 50970 Opened 24 years ago Closed 24 years ago

Filter rules doesn't show target folder location.

Categories

(MailNews Core :: Filters, defect, P3)

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: laurel, Assigned: dimator)

Details

(Keywords: regression, Whiteboard: [nsbeta3+])

Using aug31 commercial build Regression The filter rules dialog doesn't display the target folder for an existing filter having action MoveToFolder. Instead it reverts to the mail server level for the default mail account (not even the one you've selected if other than the default account). The filter rules file does write the proper value. However, if the user goes to edit an existing MoveToFolder filter's criteria and clicks OK, the user will be prompted to enter a folder destination. This is bogus. 1. Go to mail window, login to mail account, select INBOX. 2. Edit|Message Filters. 3. Click New, create a new filter with action MoveToFolder, then select a folder in the Local Folder hierarchy, that selected local folder does display in the dropdown. Confirm OK to the filter rules dialog and the main filter dialog. 4. Edit|Message Filters. Select the new filter and click Edit. Note the Action target folder selection is now the default mail acct/server level, i.e. "Mail for laurel@netscape.com". 5. Add another criteria line, or change the existing one. Click OK to the filter rules dialog. Note that you get an alert prompting for a target folder. Result: filter ui loses target folder selection. Causes confusion for user. Expected: 1. We actually shouldn't even show the server/acct as a default move action target since server level is an invalid filter destination. 2. MoveToFolder target dropdown should retain and display the folder which user selected.
Severity: normal → major
Keywords: nsbeta3, regression
Priority: P3 → P2
QA Contact: lchiang → laurel
Note: this affects the target folder display for both migrated 4.x filters and those filters created in 6.0.
*sigh* this WAS working. ... checking into it.. menulists might have busted.. AGAIN
Status: NEW → ASSIGNED
nsbeta3+, P3.
Priority: P2 → P3
Steve forgot the nsbeta3+.
Whiteboard: [nsbeta3+]
Dimi, can you take this one?
Assignee: alecf → dimator
Status: ASSIGNED → NEW
Switched the rule order, and now everything works.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
OK using sep13 commercial build linux rh6.0, NT 4.0 and mac OS 9.0
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.