Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 167927 - changes to a bug ticket do not take effect locally
Summary: changes to a bug ticket do not take effect locally
Status: RESOLVED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: Other Linux
: P2 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Robert Elves CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-13 14:50 EST by Martin Kobele CLA
Modified: 2006-12-19 12:44 EST (History)
0 users

See Also:


Attachments
what does this icon mean? (2.92 KB, image/png)
2006-12-14 14:14 EST, Martin Kobele CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Kobele CLA 2006-12-13 14:50:41 EST
scenario:

1) open an existing bug. My list of bugs are from a query which I imported by url.

2) change something in the ticket (add comment, change assignee, close it,...)
3) submit the changes

what happens now, is that
1) the window containing the bug ticket we just modified is not reloaded or even closed
2) if you close the window and double click on the bug in the task list again, the opened window is the same one as we just closed. which means, none of the changes appear to be applied. The bug was modified successfully on the bugzilla server, but not locally.
3) you have to manually synchronize the particular bug ticket and confirm that local changes are going to be thrown away. a synchronizing of the entire query is not sufficient.
Comment 1 Martin Kobele CLA 2006-12-13 14:53:22 EST
same problem if I  open a new bug ticket:
the new bug is not shown in the query list in my Task List right away. A manual synch shows it.
Comment 2 Robert Elves CLA 2006-12-13 20:04:00 EST
Can you reproduce using queries built using the query form?
Comment 3 Martin Kobele CLA 2006-12-14 08:31:48 EST
if query was built using the query form, the behavior is identical.
Comment 4 Robert Elves CLA 2006-12-14 12:57:21 EST
Upon pressing submit the report should be submitted to the repository. If submission is successful you should see the outgoing arrow go away on the task in the task list. This is followed by a synchronization of that task, followed by the editor itself closing and reopening. From your description it sounds as though this  synchronization after submit is either not happening or not completing correctly.  Try opening the progress view and submitting a change to a report and see if the sequence of jobs appears to follow what I've outlined above. Are there any errors in the eclipse error log when this failure occurs? 
Comment 5 Martin Kobele CLA 2006-12-14 14:12:59 EST
I opened the progress view and submitted a change:

it says "refreshing workspace" but that's it.
The editor does not get closed nor synchronized. I have to synchronize it manually. Synchronizing the query group is not efficient. I need to synchronize the specific task via right click->Synchronize.

The icon changes. I will attach an image.
Comment 6 Martin Kobele CLA 2006-12-14 14:14:25 EST
Created attachment 55696 [details]
what does this icon mean?

ctrl-shift-alt-? (the legend) does not reveal what this clock stands for.
is it waiting for a synch?
Comment 7 Robert Elves CLA 2006-12-15 03:21:27 EST
Yes, the clock decorator represents a synchronizing task but sometimes it sticks (bug#132725).

Martin, could you confirm a few things for us:
- that this bug relates to use of the Bugzilla editor (not Jira/Trac/etc)
- the version of Eclipse in use
- the version of Linux in use
- the version of the Bugzilla repository that you are submitting to and getting the failure
Comment 8 Martin Kobele CLA 2006-12-15 08:23:46 EST
> - that this bug relates to use of the Bugzilla editor (not Jira/Trac/etc)
correct, bugzilla.

> - the version of Eclipse in use
Version: 3.2.1
Build id: M20060921-0945

> - the version of Linux in use
SuSE 10.1

> - the version of the Bugzilla repository that you are submitting to and getting
> the failure
Version 2.20

Comment 9 Martin Kobele CLA 2006-12-15 09:03:10 EST
I just installed a bugzilla 2.20.3 on my own workstation just to confirm mylar's functionality with an out of the box bugzilla.
it works great.

so I guess our own bugzilla (partly patched) does not quite cooperate with mylar.
Comment 10 Robert Elves CLA 2006-12-18 13:01:02 EST
Okay, thanks for confirming this Martin. It is still a little strange that we aren't getting an error of some sort after submit. In order to resolve this I'd need access to the repository. Is there any public access to the repository in question? Marking this one (at least for now) as a wontfix.
Comment 11 Martin Kobele CLA 2006-12-18 14:33:04 EST
unfortunately, I cannot provide you with a public account since it is internally only.

thanks for all your efforts!
Comment 12 Martin Kobele CLA 2006-12-19 08:50:21 EST
how could I debug it myself? how could I see what is supposed to happen once a bug got submitted? is it something I have to monitor on the bugzilla server or something on eclipse?
The result might lead me to a possible bugfix for our bugzilla (which was patched)
Comment 13 Mik Kersten CLA 2006-12-19 12:44:22 EST
The easiest way would be to check out Mylar, launch a runtime workspace in Debug mode, and set some breakpoints.  Set up instructions are here:

http://wiki.eclipse.org/index.php/Mylar_Contributor_Reference#Workspace_setup