When moving a TM project to CM project , EPIC to story Linkages are lost

James Jacob May 23, 2024

I was trying to move a Team Managed Project to Company Managed Project.

Newly created a Company Managed Project. From the Team Managed Project ,   used the  Bulk move option to move the issues to the new project.

It asked a  few questions  - mainly  showing what should be the status of  certain  issues , which are already in a certain status  . Say for example  ,it is asking  whether the  issues in the  "In progress" status should be moved to  "To DO " status !!

 

I didn't find any option to  instruct  - Keep all Status and  Hierarchical relationships  AS IT IS - which I felt , should be the default behavior. 

 

When  the  issues were finally moved to the new project , I have  observed that 

1. the STATUS  of all  issues are retained as such  ,

2. but the  EPICs  were Converted to Story 

3. hence the EPIC to STORY  relationship  in the original project is Lost !!

Why does this happen ? 

 

 

1 answer

1 accepted

0 votes
Answer accepted
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 23, 2024

Hi @James Jacob , indeed you have discovered one of the challenges of migrating a TMP to CMP. You will need to rebuild those epic-story relationships in CMP manually. I have not performed one of these migrations in a long time, but as I recall when I last successfully did so I staged everything very carefully. For example, I did something like the following:

  1. stood up the CMP project
  2. added labels to each of my stories associated with a specific epic so that I would be able to discern which stories belong to which epic.
  3. I moved the Epics from the TMP to the CMP and then clean them up such that they were indeed epics
  4. I move the stories over associated with each epic separately and used book edit to connect the stories to the epic.
  5. rinse and repeat until done

I'm sure there are other ways and possibly better ways but that is what I did. Again I really never do this anymore and I rarely use TMP unless I'm sure that I will not be needing to migrate.

I realize the above doesn't help much, but didn't want to add descent from here in hopes that it will benefit others in the future..

James Jacob May 24, 2024

Hi @Jack Brickey  Thanks a lot for  your  comments . I marvel at  the methodical  approach  you took on the project Migration.

I carried out  this migration on a dummy project , which I  created for the sake of  testing the migration . I observed that the majority stuff  -  Issue status, lineage of Subtasks to their  Story's or  tasks , Worklogs registered  by the  members on  the individual  issues  -  etc. are properly migrated , but the Epic to Story / Task linkage is  missing .

I wonder why  the Atlassian architects / developers  have decided to keep  it that way . 

I intend to do the migration of one of our Live projects from TMP to CMP and  do the necessary patch-up post migration, as  you had suggested.

Just curious  - During your migration  process , did you face any other issues , that I should be mindful of ?  

Thanks again..

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 25, 2024

I cannot recall specifics but it seems there was an issue with a cascading custom field. The best approach for you is to create some test issues in your TMP project that encompass each field, Issuetype and workflow and test moving them.

Like James Jacob likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events