[Design] Fwd: [Sum] Update on Dashboard and Triage Bugs

[Mimi Yin]

Responses from Aparna and Morgen...

Begin forwarded message:

> From: Aparna Kadakia <aparna at osafoundation.org>
> Date: June 27, 2007 3:29:56 PM PDT
> To: Mimi Yin <mimi at osafoundation.org>
> Cc: design-owner at osafoundation.org, Jeffrey Harris  
> <jeffrey at osafoundation.org>, Morgen Sagen  
> <morgen at osafoundation.org>, Sheila Mooney  
> <sheila at osafoundation.org>, Katie Capps Parlante  
> <capps at osafoundation.org>
> Subject: Re: [Sum] Update on Dashboard and Triage Bugs
>
> Mimi,
> Many thanks for summarizing everything so eloquently below.
>
> There is one more bug to add to the list of open bugs. I am seeing  
> conflicts on some of the inbound email where it says the change was  
> done by empty at example.com instead of a real user.
>
> Bug 9603 : pending changes dialog shows empty at example.com changed  
> something..
> https://bugzilla.osafoundation.org/show_bug.cgi?id=9603
>
> Aparna
>
> On Jun 27, 2007, at 11:22 AM, Mimi Yin wrote:
>
>> Sheila asked me to compile an update on all of the Triage -  
>> Dashboard related bugs. I believe there are still a couple of  
>> things that are making it so that items are being marked as unread  
>> and popping into the NOW section when they aren't supposed to.  
>> This unexpected behavior was originally tracked in bug 9193, which  
>> was closed when we isolated 2 causes:
>>
>> 1. Bug 9484:  Edits that affected the master event in a recurring  
>> series marked the master event as having been edited, which in  
>> turn was being inherited by all instances, whether or not had  
>> actually been affected by the change. Grant has fixed this.
>>
>> 2. Bug 9305: Different Chandlers sometimes end up storing the same  
>> email address in different ways (test at example.com versus <test>  
>> test at example.com), which was causing 'bogus' conflicts which in  
>> turn popped affected message items to the top of the NOW section.  
>> bkirsch has fixed this.
>>
>> However, Sheila and I came across this behavior again and logged  
>> bug 9643. What was curious is that I would sync, get a bunch of  
>> stuff in NOW, Purge and then Sync again and get the same stuff  
>> back into NOW. When I inspected the byline to see if there were  
>> legitimate edits, the byline would claim that the last edit was  
>> made 5 days ago! We've identified a couple of additional causes:
>>
>> 1. We're sending changes to the master event's triage status when  
>> syncing, which in turn changes the triage status of all instances  
>> in the series, even if they haven't been changed. ?? I think this  
>> description is not quite right, Jeffrey / Morgen could you fill  
>> this in? Jeffrey and Morgen are working on a fix for this.  
>> Jeffrey / Morgen: How do we test this? When does the master  
>> event's triage status get changed?
>>
>> 2. Bug 9679: Adding and moving items between collections was  
>> marking items as edited, but not affecting the byline. This  
>> explains why items would pop into NOW for me, but the byline would  
>> say that the last time they were edited was 5 days ago. Adding and  
>> moving items between collections shouldn't count as editing the  
>> item and also shouldn't count as a sharing edit since 'Appears in'  
>> is not a shared attribute. Grant is working on this.
>>
>> There were also a couple of other bugs I've logged recently having  
>> to do with weirdness in the Dashboard, but no one has been able to  
>> reproduce them: bug 9646 and 9313. If anyone else has noticed  
>> this, please amend these bugs. Admittedly, I don't think I've  
>> noticed bug 9313 in a while.
>>
>>
>> BUG LIST
>>
>> OPEN BUGS
>> [Bug 9643] Recurring items unexpectedly being marked as unread and  
>> popping into NOW on office calendar
>> http://bugzilla.osafoundation.org/show_bug.cgi?id=9643
>>
>> [Bug 9670]  New: Adding / Moving item between collections should  
>> not count as an edit on that item
>> http://bugzilla.osafoundation.org/show_bug.cgi?id=9670
>>
>> [Bug 9646]  New: Bobby's PTO keeps popping into NOW in the office  
>> cal - Dashboard
>> http://bugzilla.osafoundation.org/show_bug.cgi?id=9646
>>
>> [Bug 9313] Items with pending changes are not popping to the top  
>> of the NOW section
>> http://bugzilla.osafoundation.org/show_bug.cgi?id=9313
>>
>>
>> RECENTLY RE-OPENED
>> [Bug 9502] Email I drag into Chandler via Chandler Events IMAP  
>> folder gets duplicated
>> http://bugzilla.osafoundation.org/show_bug.cgi?id=9502
>>
>> RESOLVED AS FIXED
>> [Bug 9645]  New: Who column not displaying attr name for items in  
>> Office Cal
>> http://bugzilla.osafoundation.org/show_bug.cgi?id=9645
>>
>> [Bug 9193] Items I edited or sent are being marked Unread when I  
>> sync the shared collection they were in
>> http://bugzilla.osafoundation.org/show_bug.cgi?id=9193
>>
>> [Bug 9484] Edits to individual instances are affecting the entire  
>> series
>> https://bugzilla.osafoundation.org/show_bug.cgi?id=9484
>>
>> [Bug 9305] erroneous conflict on sending an invite from a shared  
>> collection
>> https://bugzilla.osafoundation.org/show_bug.cgi?id=9305
>
Begin forwarded message:

> From: Morgen Sagen <morgen at osafoundation.org>
> Date: June 27, 2007 11:31:28 AM PDT
> To: Mimi Yin <mimi at osafoundation.org>
> Cc: Aparna Kadakia <aparna at osafoundation.org>, Jeffrey Harris  
> <jeffrey at osafoundation.org>, Sheila Mooney  
> <sheila at osafoundation.org>, Katie Parlante <capps at osafoundation.org>
> Subject: Re: [Sum] Update on Dashboard and Triage Bugs
>
>
> On Jun 27, 2007, at 11:22 AM, Mimi Yin wrote:
>> 1. We're sending changes to the master event's triage status when  
>> syncing, which in turn changes the triage status of all instances  
>> in the series, even if they haven't been changed. ?? I think this  
>> description is not quite right, Jeffrey / Morgen could you fill  
>> this in?
>
> I think that is a correct description, and Jeffrey is working on a  
> fix for this leaky master triage.
>
>> Jeffrey and Morgen are working on a fix for this. Jeffrey /  
>> Morgen: How do we test this?
>
> When Jeffrey is done with the fix we will have unit tests to ensure  
> master triage is not shared.
>
>> When does the master event's triage status get changed?
>
> I'm not sure what triggers it.
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/design/attachments/20070628/d05b8fff/attachment.html