How to split an existing project in two, keeping worklogs and versions intact?

[Lisa Reilly]

Hi there,

I have a project with about 60 Epics and 100 versions.

About 75% of the issues in the project relate to 2013 work. We would like to 'split' the project in 2, so that I have PROJECT 2013 and PROJECT 2014.

However, if I move all of the 2014 issues from PROJECT 2013 to PROJECT 2014 I lose the FixVersions.

One of the drivers for doing this is because when a user creates a new task in the current project, they have 60+ Epics to select from (Epic Link needs to be mandatory for issue creation for this projct) and this is cumbersome.

Any suggestions? I want my worklogs and FixVersions to remain intact!

Thanks

[Boris Georgiev [Appfire] · Accepted solution]

You can try to create a clone of the existing project into a new one and then remove everything that is not needed from both projects (the 2013 and 2014).

Create an xml backup of JIRA and then replace the project key (i.e. PR) with a new one (PRI). The patterns you need to search are (not sure these are all though)

• key="PR
• projectKey="PR"
• key="PR"
• originalkey="PR"

After replacing these in the entities.xml try do Project Import from backup. This will create a new project with key "PRI" which should be the same as the "PR" project. Then remove all that is not needed.

NOTE: This is not tested and is a solution that "might" work, so I'm not sure if JIRA Agile will work correctly after that with the new project and if actually the JIRA Agile data will be properly cloned, so you have to have a backup of your system in case something goes wrong or test this on a snadbox/test/staging JIRA instance.

Some plugins like CLI or Script Runner provide clone functionality and you may also try to do the clone using them.

[Lisa Reilly]

Hey Boris - looks like that Script Runner plugin will work for me. Thanks for your answer.

[Lisa Reilly]

Hey Boris

Turns out this doesn't work because worklogs aren't copied. Any other ideas??

[Lisa Reilly]

Yes, it doesn't clone the worklogs for the tasks?

[Boris Georgiev [Appfire]]

Do you mean Script Runner ?

[Boris Georgiev [Appfire]]

And a possible way to avoid editing the backup xml manually will be to restore the JIRA backup onto another JIRA instance, change the project key and then create a backup again which to use for import into the original JIRA, but into a different project

[Boris Georgiev [Appfire]]

I suspected that it will not copy worklogs and that's why I've suggested using project backup/restore approach.