Team to Company Managed move has removed all Epic children

[Ben Weisman]

Is this a known issue? It didn't move the Epics it was supposed to but moved everything else, removing the connection.

It seems like when you update a child task within an epic it provides an update in the history section of the Epic. Can I use this to piece this back together??

[Joseph Chung Yin]

@Ben Weisman -

Hi Ben:

What do you mean by "It didn't move the Epic but moved everything else" + "removing the connection"?

Please clarify your ask with more information, so we can advise.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

[Ben Weisman]

@Joseph Chung Yin For some reason when I bulk moved everything from a TMP to CMP project it didn't move the Epics. So everything got disassociated from them. Do you know why this happened and how I can avoid it? I need to move another project.

[Jack Brickey]

If you move a single epic and it's children it will  work as it prompts you thur the necessary info to succeed. I do not believe this will succeed with multiples though I have not recently attempted.

[Ben Weisman]

@Jack Brickey Why is the logic set up this way? This project has 1,000 tasks and 50 Epics. I assume if I move the Epic it will not automatically move all the stories within it to the new project as well?

I'm hoping you can give me a workflow/process to successfully move this project over (as efficiently as possible). Thanks!

[Jack Brickey]

Hi @Ben Weisman , regarding my last statement where I didn't believe moving multiple Epic would succeed I thought it would be best to actually test this for myself. Whether the results have always been this way or have changed recently I cannot say. Please note the following is based on a premium tier test instance but I would suspect that it is basically the same in standard. One thing I will note here is that the user interface presented during the bulk change operation between premium and standard is certainly different.

With that out-of-the-way, here are my findings.

Test scenario:

• Create to test epics each with associated test stories in a TMP project
• Bulk move all issues to a CMP project
• Observe results

Results:

1) JQL to resolve desired issues for move

2) Move operation details

3) Details of Epic Move requiring the singular Epic Name

4) Confirmation of pending move

5) We have two Epics with a single Epic name

6) And all issues will reference the same Epic link but for different Epic issue key

Conclusion:

You can in fact achieve the move but there are undesirable (?) results in the Epic name and Epic link.

[Ben Weisman]

Thanks for this @Jack Brickey . I think the Epics may have been disassociated because Epic name is a required field within the CMP projects but doesn't exist in TMP. Could this be the reason?

[Jack Brickey]

yes indeed that is true.

[Joseph Chung Yin]

@Ben Weisman -

The main issue here based on my further analysis is that TMP only focuses on the issues within the same project (cannot create EPIC links among different projects), where as CMP projects will allow you to establish EPIC links among different CMP projects.

So, the only solution that I can think for you to try is the following -

1) From TMP project, move all the EPICs into your CMP project first.

2) Before the move, generate a report showing the parent/child links to be used as a reference.

3) Use the report in #2, conduct your move of your child stories into the CMP project.

Again, TMP project is complete localized in focus.

Hope this makes sense.

Best, Joseph

[Jack Brickey]

Epics in TMP is quite different than CMP. The way to do this is to create a new epic in the CMP, move all issues over then add the new issue into the newly created epic. You can use bulk update if desired.