The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Lost Epic Children during import

Rachael Garbee
Contributor
September 22, 2020

To move a Next Gen project to a Classic you must export your data and then import it into a new Classic project. I have done this multiple times today and each time am unsuccessful on some level. I've reached my breaking point and am reaching out for help. During my import I am losing all the children that are associated to an Epic. I have ensured the fields are visible on the new board and I have named and mapped them in the CSV and the fields during import. However, every time I import I lose the parent/child association between an Epic and its tasks. 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Abhinaya Sinha
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 23, 2020

Hi @Rachael Garbee have you tried moving issues rather than doing import/export? We have done work in preserving epic links when moving issues. So curious to know if it works for you. Thanks.

Rachael Garbee
Contributor
September 25, 2020

I'm afraid to use the move functionality b/c if information is lost during the move I cannot get it back. Do you have thoughts on that?

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events