Drag & Drop contacts does not work

[Klug]

Hello all.

Could anyone test this before opening a bug ?

I setup the ZCO on my Outlook yesterday (before that, I was using Outlook only as a backup of my Nokia 9300).

I had some contacts in the "Personal Folders".

In order to sync them with Zimbra, I did a drag & drop of the contacts into the "Contact" folder (the Zimbra one). I forced sync (F9) and checked with the WebUI : nothing... I stopped/started Outlook, still nothing.

So I made another test : I created a new contact and synced.
This contact was correctly synced, it's in the WebUI, no problem...
The other contacts were not synced and I still can not see them in the WebUI.

[sam]

cross store move is now fixed. See this bug 6530 for more details.

[Klug]

Yep, got the mail from bugzilla.
Thx.

[njw]

Looks like this bug affects email drag-and-drop as well as contacts and was reopened with the introduction of 4.5.3_GA. Is there any way to obtain previous releases of the Outlook Connector until the bugfix propagates to the next general release and would this even work? This one is a show stopper for us.

[sam]

the bug only pertains to moving items between 2 outlook stores. previous versions are not available.

[njw]

I see that this bug isn't fixed in 4.5.4_GA (just released) even though its status is RESOLVED. Please tell me that we’re not going to have to wait for late summer (target for Franklin) for a fix to something so basic.

[jholder]

Did you update your connector?

[njw]

yes, currently using ZimbraOlkConnector-4.5.4_GA_762_4.5.189.msi

[sam]

First, this is for dragging and dropping items between a PST and a Zimbra MAPI service. Dragging and dropping between folders of a single Zimbra MAPI service has no issues.

You might have to wait. Its a rather large change and usually large changes don't make it to the maintenance releases. We'll review the risk involved again and see if we can get it out sooner.

[njw]

checking on the status for bug 6530, I notice that it still appears as RESOLVED, FIXED. Could you please reopen the bug until it is fully resolved?