Comment 1 Mik Kersten 2007-02-01 19:50:56 EST

I did a quick test and it worked with our test task (JDB-100) and it worked.  Reopen if it is still failing for you.

Comment 2 Eugene Kuleshov 2007-02-01 20:00:14 EST

It does not work for Codehaus jira repository http://jira.codehaus.org

I just tested with the head version. When you create query on some project, i.e. Maven 2.x Extension for Eclipse, on all bugs, the closed ones does not appear with your favorite striketrough. So, it should be very easy to notice that for you. ;-)

Comment 3 Mik Kersten 2007-02-01 20:17:44 EST

I just ttested and yes, there appear to be some failures with synchronizing tasks with codehaus.  I kept getting "Task Data not availble" and a lot of the following output (which your reported previously).  I'm not sure that I'll have time to look at this next week so marking "helpwanted" for now.

Unknown Issue attribute: attachments
Unknown Issue attribute: subtasks

Fyi, I just uploaded build 1.0.1.v20070201-1700.

Comment 4 Mik Kersten 2007-02-01 20:21:15 EST

Steffen: are you seeing this?

Comment 5 Eugene Kuleshov 2007-02-01 21:07:23 EST

By the way, JDB-100 also does not appear with striketrough in the task list.

Comment 6 Mik Kersten 2007-02-01 22:22:05 EST

It does for me.  I closed and reopened it today, so maybe it wasn't synched.

Comment 7 Eugene Kuleshov 2007-02-01 23:01:34 EST

Weird. I had to delete query, then repository to get it all cleaned up here.

PS: Then I tried to delete bunch of old tasks and now looking at this crazy Task List flickering. Mik, are you plsnning to fix bug 165880 any time soon?

Comment 8 Mik Kersten 2007-02-05 15:44:54 EST

I doubt that we'll be able to do bug 165880 for 2.0M1, but hopefully soon thereafter.

So is it working for you now?  I have no idea why re-creating the query would have solved anything, but I can't reproduce.

Comment 9 Eugene Kuleshov 2007-02-05 16:40:22 EST

Apparently not. I just changed some query to include closed tasks and they did come back without striketrough.

Maybe it is because those query hits didn't have tasks. I suspect that JIRA's synchronization does NOT update attributes, including status, upon synchronization. So, as a result Task List is don't know about it. Though it does not explain why I do see status Closed in the JIRA form editor.

Comment 10 Steffen Pingel 2007-02-05 17:06:06 EST

Yes, I have seen this error, too. I have to explicitly synchronize closed Jira tasks for Mylar to recognize the status change.

Comment 11 Mik Kersten 2007-02-07 21:01:06 EST

Steffen: are you interested in investigating?

Comment 12 Steffen Pingel 2007-02-12 20:22:00 EST

Created attachment 58817 [details]
mark completed query hits as such

Set completed status was never set.

How do you feel about adding me as a committer on the JIRA plug-ins to avoid the overhead of merging patches?

Comment 13 Steffen Pingel 2007-02-12 20:22:01 EST

Created attachment 58818 [details]
mylar/context/zip

Comment 14 Eugene Kuleshov 2007-02-12 20:33:12 EST

(In reply to comment #12)
> Created an attachment (id=58817) [details]
> mark completed query hits as such
> 
> Set completed status was never set.
> 
> How do you feel about adding me as a committer on the JIRA plug-ins to avoid
> the overhead of merging patches?

+1

Comment 15 Eugene Kuleshov 2007-02-12 23:15:00 EST

Patch applied. Thanks Steffen.

PS: I always wanted to use "apply patch" action from the attachments, it rock!

Comment 16 Mik Kersten 2007-02-13 17:10:21 EST

Eugene: note that when you apply patches from non-committers (i.e. not in this case) you have to update mylar-iplog.csv.

Comment 17 Eugene Kuleshov 2007-02-13 18:37:56 EST

Aye sir!