Jira Tickets Migration

[Roopa V]

Hi Team,

We have created a new kanban project jira board(ZZZ) with better optimization.

Now we want to move issues from old jira kanban project board(YYY) to new jira board(ZZZ).

We want to decomission or archive old jira project (YYY) without loosing any History and Data.

What is the right way to do it? Please suggest the steps.

Note : Trashing a project will delete data after 60 days. so I think this is not the right approach.

Best Regards,

Roo

[Walter Buggenhout]

HI @Roopa V,

It is quite important to be clear what you mean by board and project. Your issues are stored in a project, while a board just adds a visualisation and feature layer on top of that.

Assuming that you have created a new project (I am guessing by your reference to ZZZ and YYY, which I suppose represents the project keys). The logical way to move your issues from the old project into the new, is moving them via a bulk operation. You can find more details on how to do this in this support article.

Moving your issues will do so including all issue history. Be aware that after moving the issues, there will be nothing left in the old project (apart from the project configuration). So it is perfectly fine to even delete the old project after the issue move, since all your data will be in the new project.

One important remark: before you perform the move, check if both projects are of the same type (team managed / company managed). Moving issues from a team managed project to company managed may cause data loss. If you are in this situation, check out this support article to learn more about potential issues during the migration.

Hope this helps! 

[Roopa V]

Hi Walter,

Thank you for your response.

In clear, I want move issues from old project to new project.

New custom fields are added and mandated in new project. So we are going to issues from old project and importing to new project with specific fields.

Now, after I export required tickets from old project, I need to decommission that project without  loosing any data and history (it should not be used by users and users start sing new project).

[Walter Buggenhout]

Yes indeed. Thanks for clarifying. That is the scenario I had in mind. But - as I described - you don't need to export anything; just move the issues into the new project with bulk move. Then get rid of the old project.

[Roopa V]

Okay. But the fields mandated in new project are not available in old project and vice versa. Also workflow, status etc is different in new project .. Old project has different workflow.

I want to move issues with only specific fields.. Bulk move works in this case?

[Els Bassant]

Hi Roopa, 

You can create multiple boards for a jira project. So depending on your circumstances you may not need a new project.

If the configuration of the projects ZZZ and YYY are the same the only thing that you have to do is create a new board. When creating a new board you can choose to base it on an existing project. If you only want to work from 1 board in the project you can delete the old board once you've finished configurating the new one. See this documentation for more info.

If the configuration of projects ZZZ and YYY are different you can use bulk edit to move all  issues / the relevant issues from the old project to the new one. While moving issues some data may be lost, I suggest reading this documentation before moving any issues. It is aimed at moving issues between Team and Company managed projects, but much of it holds true for moving between any project.

Project archiving is only available on Premium and Enterprise plans.

Hope this helps, 

Els