[chandler-users] #7894: not "purged" to the DONE section

[Rick Rawson]

Mimi,

I tried to reproduce this behavior using my Scratch collection, which 
does not reside on the server. I failed. So, I copied an offending event 
from a published collection to Scratch and deleted (Removed) the event 
from the original, published collection. That event behaves the same way 
in the Scratch collection when I SYNC, even though the Scratch 
collection is not connected to the server. In other words, it is marked 
as DONE, triages to the DONE section, but rises to the NOW section upon 
SYNCing. However, upon SYNCing a second time, the event remains in the 
DONE section, as it should.


Rick


Mimi Yin said the following on 2/8/2008 5:24 PM:
> Hi Rick,
>
> Hm, triaging an item to DONE until a future alarm date fires is  
> *supposed* to work.
>
> I wonder if you are experiencing one of the many pop-to-now bugs  
> we've been trying to track down over the last few months: http:// 
> chandlerproject.org/Planning/OneDotZeroWorkQueue#PopToNowBugs
>
> It would be interesting to know if you can reproduce this situation  
> with items that aren't on the server.
>
> Mimi
>
> On Feb 8, 2008, at 1:42 PM, Rick Rawson wrote:
>
>   
>>> The bugs fixed in this release include:
>>>
>>>
>>> #7894 Events should be marked as DONE when end-date/times roll by,  
>>> but  not 'Purged' to DONE section
>>>
>>>       
>> I think I am seeing, perhaps, an unwelcomed sequela of this bug  
>> fix. Today is 2/8. I have a task that was dated 2/11 (date in the  
>> traige table) and a tickler set for 2/11, but which I accomplished  
>> early. I set the triage status to DONE, patted myself on the back,  
>> clicked TRIAGE, and watched that task get moved to the DONE  
>> section. Then I SYNCed.
>>
>> That task came back, still marked as DONE, but now located in the  
>> NEW section. The only action that prevented this from happening was  
>> changing the tickler alarm from 2/11 to 2/8. I can understand why  
>> Chandler might mark tasks/events as DONE if the end-date/time rolls  
>> by, but it seems that UNTIL the end-date/time rolls by, Chandler  
>> still considers the task/event NOT DONE, regardless of the triage  
>> status. I suppose, logically, Chandler is asking HOW CAN IT BE  
>> DONE?, if the completion date is still in the future. There seems  
>> to be a conflict between logic and reality.
>>
>>
>> Rick
>>
>> P.S. Substituting LATER for DONE in the above description changes  
>> nothing. I tried that, too.
>>     
>
> Which do you mean by 'changes nothing'? The weird behavior you see  
> above is the same regardless of whether you triage the item to DONE  
> or LATER. Or substituting in LATER doesn't produce the weird behavior?
>
>   
>> _______________________________________________
>> chandler-users mailing list
>> chandler-users at osafoundation.org
>> http://lists.osafoundation.org/mailman/listinfo/chandler-users
>>     
>
> _______________________________________________
> chandler-users mailing list
> chandler-users at osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/chandler-users
>   

-- 
Richard E. Rawson, DVM, PhD
Senior Lecturer
T8-008C Veterinary Research Tower
Department of Biomedical Sciences
College of Veterinary Medicine
Cornell University | Ithaca | NY | 14853
T 607-253-3748 | E: rer1 at cornell.edu <mailto:rer1 at cornell.edu>