On 10/5/07, Mimi Yin <[EMAIL PROTECTED]> wrote: > > Since 0.7.0.1, I've noticed that there are still a few bugs obscuring the > Triage experience by generating false positives: False positives of items > that think they were edited, but weren't. Basically, every time I sync, I > get anywhere between a dozen to many dozens of false-positive items in the > NOW section. (This is most true on the Office Calendar where there are a lot > of recurring events.) > > I think it's important we nail these in an effort to better support current > users before moving onto feature add-ons. > > There's also 1 Sharing bug that can be a bit paralyzing, but don't know how > prevalent it is. > > These are the 5 problems I know about, I'm not sure if there are more. > Please pipe up if you do! > > 1. 'from' EIM field is causing items to be marked as edited/ in conflict > that aren't really (at least not in a way the user can see) > https://bugzilla.osafoundation.org/show_bug.cgi?id=10799
I see this is targetted at 0.7.future -- should it be 0.7.2? > 2. Reload bug that screws up triage status when people dump/reload shared > collections. Bug#? There was a bug where the (incorrect) order of items being exported was causing problems during subsequent reloads, but over time this should go away as people move to the new code. > 3. Entire series pops into NOW all the > time: https://bugzilla.osafoundation.org/show_bug.cgi?id=10948 I spent a bunch of time on this one yesterday (oh, and I see it's actually an untargetted bug), and it seems that we just need to ignore the doAutoTriageOnDateChange value when deciding to mark an item unread. This is already part of bug 10799. > 4. I unstamped a recurring series. And then after I synced, it re-appeared > at the top of NOW as unread and had re-stamped itself. But I was still list > as the last person to edit it. Now if I try to stamp it again, I can't get > anything to stick in the To: > field. https://bugzilla.osafoundation.org/show_bug.cgi?id=10980 That one sounds fun. I would definitely upload a repo for that bug. > 5. Sharing bug: I delete an item on a shared collection. I sync, it comes > back. (Is there a bug for this already?) Well, when this happens it means there are inbound changes for the item, so we bring the item back. So we need to figure out why the server is sending you changes. Please file a bug with repo and logs. ~morgen _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
