Bug 702298

Summary:	Subfolders are forgotten on folder move
Product:	[Fedora] Fedora	Reporter:	Heiko Adams <bugzilla>
Component:	evolution	Assignee:	Matthew Barnes <mbarnes>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	15	CC:	lucilanga, mbarnes, mcrha, reklov
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-05-09 16:27:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Heiko Adams 2011-05-05 10:13:35 UTC

Description of problem:
When moving a folder, which has at least one subfolder, to a new location the subfolders are not moved and it seems they are lost.

Version-Release number of selected component (if applicable):
evolution-3.0.1-1.fc15.i686

How reproducible:
allways

Steps to Reproduce:
1. move a folder which has subfolders to a new location
  
Actual results:
The subfolders are not moved and it seems they are lost

Expected results:
The subfolders should be moved too

Additional info:
Moving the folder back to it old location brings back the subfolders

Comment 1 Milan Crha 2011-05-05 12:06:35 UTC

Thanks for a bug report. What is the account type you are moving folders from/to, please? By account type I mean local (under On This Computer), IMAP, IMAP+, Exchange, MAPI, ...

Comment 2 Heiko Adams 2011-05-05 12:34:45 UTC

I'm using exclusiv POP3 to fetch my mails.

Comment 3 Volker Sobek 2011-05-07 11:48:08 UTC

Sounds like this one: https://bugzilla.gnome.org/show_bug.cgi?id=648454

Comment 4 Milan Crha 2011-05-09 16:27:19 UTC

Thanks for the update. I agree with the upstream bug, and I'm moving this one there. Please see it for any further updates.

Comment 5 Heiko Adams 2011-06-18 11:31:36 UTC

The bug has been fixed upstream