Using may23 m16 commercial build Anything you change (New Filters or edits) in the message filters UI is for that session only. Need to make it save changes upon OK to rules.dat. This really makes it hard to get through functional testing. Please do this SOON.
Added P1 priority, dogfood and nsbeta2 keywords. Must have this functioning ASAP.
Keywords: dogfood, nsbeta2
Priority: P3 → P1
Putting on [dogfood+] radar.
aw shoot, it was saving a few days ago. :( I think this means we're leaking servers.
Status: NEW → ASSIGNED
Hmm... no comment on this bug in a week... and it is listed as a dogfood stopper (should be a Real High priority). Can you put the ETA for the landing of the fix in the whiteboard? Thanks, Jim
I can see why this is a test blocker for the specific functionality of preserving filters across sessions. Does that make it dogfood somehow? The absence of the entire filter UI was not dogfood for beta1...
I nominated for dogfood, maybe I shouldn't have. Feel free to knock the dogfood rating off... It is a definite functional testing blocker, but not a basic stability blocker. I just didn't want this major portion of a new feature to slip to being fixed for beta at the edge of the beta2 deadline.
We want this to be in as soon as possible so that Laurel can test this feature in time for beta2. Now that beta2 is pushed out, we still have some time.
Whiteboard: [dogfood+] → [dogfood-][nsbeta2+]
ok, basic bandaid fix is in - if you hit OK in the filter list dialog, it will save the current list of filters to disk...
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
Wait... does "bandaid" mean it's a temporary fix? I also want a heads-up if you fix it again (not that anything would break, no, no way).
bandaid in that it will work for beta2, and FCS.. the way I fixed it wasn't very friendly to the filter architecture, but it works.
OK using 2000-06-05-08 commercial build linux rh6.0, NT 4.0 and mac OS 9.0
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.