This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 179873 - Completed status not correct for JIRA tasks
Summary: Completed status not correct for JIRA tasks
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 2.0 M3   Edit
Assignee: Steffen Pingel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 180288 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-03-28 19:23 EDT by Steffen Pingel CLA
Modified: 2007-05-02 00:44 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steffen Pingel CLA 2007-03-28 19:23:33 EDT
The completed status of JIRA tasks is not correctly synchronized between task data and JiraTask objects.
Comment 1 Steffen Pingel CLA 2007-03-28 19:36:57 EDT
This is not as easy to fix as I thought. We only store the name of the status in a RepositoryTaskAttribute and we would need to map it to a Status object from the repository configuration in JiraTask.isCompleted() to determine the completed status. Not sure if it is worth implementing that now considering that the whole API is going to change in 2.0M3.
Comment 2 Eugene Kuleshov CLA 2007-03-28 20:00:51 EDT
I came to the same conclusion. Mainly because JiraTask don't have link to the jira repository.
Comment 3 Eugene Kuleshov CLA 2007-03-30 18:23:23 EDT
*** Bug 180288 has been marked as a duplicate of this bug. ***
Comment 4 Mik Kersten CLA 2007-03-30 18:26:24 EDT
Steffen, Eugene: is this a regression from 2.0M1?
Comment 5 Eugene Kuleshov CLA 2007-03-30 19:00:55 EDT
(In reply to comment #4)
> Steffen, Eugene: is this a regression from 2.0M1?

It is unclear. The synchronization works sometimes. It is possible that issue is either depend on particular workflow or specific to particular jira version or customization.
Comment 6 Mik Kersten CLA 2007-03-30 19:57:31 EDT
I can't reproduce it with developer.atlassian.com:

JDB-100: test Mylar editor integration
http://developer.atlassian.com/jira/browse/JDB-100
Comment 7 Jörg Thönnes CLA 2007-03-31 02:14:25 EDT
With my JIRA repository at https://www.quickfixj.org/jira it definitely works with 2.0M1, but stopped working with the
dev build 20070330-8000. The above JIRA site is from an open source project, so you may get an account and ask Steve Bate
whether you may test. But it is not needed to change anything to see the behaviour. Just status before 2.0M1 and after.

Until this is working again, the newer Mylar is of much less use for me.
Comment 8 Jörg Thönnes CLA 2007-03-31 04:59:28 EDT
The Completed status is not synched for the newest milestone build 20070330-2000 (2.0M2 ??).

With 2.0M1 this worked fine for JIRA Enterprise Edition, Version: 3.6-#153.

Anything I could do to provide further details?
Comment 9 Jörg Thönnes CLA 2007-04-01 16:06:03 EDT
 (In reply to comment #5)
> (In reply to comment #4)
> > Steffen, Eugene: is this a regression from 2.0M1?
> It is unclear. The synchronization works sometimes. It is possible that issue is
> either depend on particular workflow or specific to particular jira version or
> customization.

The same happened to me: After a while (I did not notice how) the completion status is synced correctly.
At the moment, this is OK. But it is hard to notice when it goes out of sync again (if it happens!).
Comment 10 Eugene Kuleshov CLA 2007-05-01 23:00:38 EDT
Steffen, did you just fix this in another issue?
Comment 11 Steffen Pingel CLA 2007-05-02 00:44:05 EDT
Sorry, I accidentally swapped the issues. Quoting bug 171107, comment 8:

Finished implementation of JiraRepositoryConnector.updateTask() which should now set the completed state.
Comment 12 Steffen Pingel CLA 2007-05-02 00:44:35 EDT
Resolving