Lost tickets when coping over an epic from 1 board to another

[marieamymitchell]

Hello,

How can i find missing tickets, which did not bulk copy when transferring an epic from 1 project board to another?

There was a message to check the jira logs, but then the transaction completed with only some of the tickets moving over. 

Thank you

[Trudy Claspill]

Hello @marieamymitchell 

Do you mean that you moved tickets to a different project with these actions?

1. Used the Advanced Issue Search to select issues.

2. Used the Bulk Change option

3. Selected the Move operation

If those were not the actions you used, please tell us the steps you used to move the issues.

If you have the original issue keys for the tickets you were trying to move you can enter the key into the Quick Search field and the issue should come up.

Did you receive some sort of error message during the process? If so what was the exact error message?

[marieamymitchell]

Hello @Trudy Claspill

Thanks for getting back to me.

From the epic, i selected 'move' and chose to 'move child issues' so all tickets would move with it.

I don't have the original ticket numbers for all listed under the original epic i'm afraid.

There was some messaging during the transfer process to 'check jira the logs' but then the action completed.

[marieamymitchell]

Sorry I should have also added @Trudy Claspill - the reason this happened is because i did not change the status mapping i.e 'In Progress' on one board means 'In Development' on the new one (as the boards have different workflow) - i thought i could do this later.

[Trudy Claspill]

The History tab for the Epic should provide you with all the information about child issues being added to or removed from the Epic. You should be able to look through that to get all the original issue keys for the child issues.

[marieamymitchell]

Thank you @Trudy Claspill - that works! :)

[marieamymitchell]

@Trudy Claspill - oh wait no, it's only giving me the history of tickets that have copied over in the epic, not the ones that haven't.... 

[Trudy Claspill]

I'm going to try to recreate your scenario.

Were the Epic and Child issues all in the same project originally?

Was the source project Company Managed or Team Managed?

Was the destination project Company Managed or Team Managed?

[marieamymitchell]

Thank you!

Yes - epic and child issues all in the same project, and both projects are company managed.

[Trudy Claspill]

I did make sure my scenario include a child issue that had a Status value that was not available in the destination project.

I am a Jira Admin for my environment. I don't know if that impacted my results.

Attempting to recreate your scenario I did not "lose" any issues. When I look at the moved Epic it still has all the child issues it had before the move.

How have you determined that the child issues got "lost"?

One thing I did notice was that the status from the original project that was not available in the destination project was actually added to the destination project by the move process. That may have occurred because I am a Jira Admin and therefore have permissions to modify the workflows. In my agile board, the new status shows up in the Unmapped Statuses column currently, so the issues in that status don't display on the board. Moving the unmapped new status to a column of the board will make the issues in that status appear.

Are you a Jira Admin in your environment? It will take me a while longer to try to replicate this scenario for a user moving issues that is not a Jira Admin.

[marieamymitchell]

Thanks for your help @Trudy Claspill 

I'm not a Jira admin no, but I have compared the workflows and can't see any reason why they wouldn't transfer to an (existing) status on the new board. 

I'm purely basing this on how many i saw by eye in the original epic v how many have transferred. I'm hoping it's just tickets marked as 'wont do'.

Thank you very much for your help, but don't worry, happy to leave the investigation here.