Bulk migrating ticket issue to another project - Impacts on historical data?

[Edmond Dang]

Hi team,

I was curious to understand how migrating ticket issues to another project works. I have created a brand new Kanban board in a new project for our team. What happened was that I realized the old board we were working out of was actually an Agility board. I did some scoping online and found out that there is no way to turn an Agility board into a Kanban board (if this is possible let me know.)

With that said, I had the idea of just creating a brand new project/board and bulk migrating the issues in our old project to our new board in the new project. However, before doing so, I wanted to ensure that all the previous historical data will remain within those issues and nothing will be erased. Can somebody confirm this?

For reference, if our team decides to see all the solved tickets, we can easily look into the data for the issue ticket from the past (when it was in our old board) without worrying that it was erased. 

Thanks!

[Fabian Lim · Accepted solution]

Hi @Edmond Dang

We have done this previously and no data will be lost and all history will be kept since boards are just filters. However, if those issues were in some sort of previous sprints some of the old reports could be adfected.

Just make sure that before your bulk move you know how the old project workflow statuses will be mapped in the new project.  I would recommend you keep the same workflow so you dont have an issue.

Also ensure that all fields available in the old project exist in the new project screens or you won't be able to edit/view them.

Good luck.

[Edmond Dang]

Hi @Fabian Limhanks for your reply! 

I just wanted to clarify some stuff to be 100% sure. After a closer look into it, I realized that it may not be because the old board was an agility board. It's still a Kanban board style but it seems like it's a team-managed board/project compared to my new board which is a company-managed board/project. That seems to be the only difference and why there are so many limitations in the old board.

With that said, the new project's workflow should be relatively similar in the sense that, it'll have the same Issue Statuses as the old board "In progress", "Done", " In triage", but with a few new Statuses added to it. The only difference I would say would be the fact that the issue types are different.

Let me know if you see any other issues here!

[Edmond Dang]

To answer your concern from before, we don't work out of sprints so we should be okay there!

[Fabian Lim]

You should be ok. Just test it out with one test ticket and you will found out.