How to clone/copy an issue and retain the comments in Jira Data Center

[Mike Gourley]

Background:  We are preparing to migrate some projects from one Jira Data Center to another.  We are not migrating the JSM projects, only the non-JSM projects.  CMJ is being used to perform this task.  We have discovered that some issues originally logged in a JSM project were moved to a non-JSM project.  The CMJ tool now demands to install JSM on the target Data Center for the migration which we do not want to do.

Question:  How work around this problem?  If we clone the issues in the non-JSM project will that de-link their connection to JSM?  If so, we now realize the Comments will be lost by the clone function and these issues have extensive Comments.

At this point we are faced with manually re-creating these issues, and all their comments, in the non-JSM projects in order to disconnect them from JSM so that the migration can proceed.

Any suggestions for making clones or copies of these issues that will retain what we want from the issues including comments and links without dragging along internal history from JSM?

[Ste Wright]

Hi @Mike Gourley 

Is it not possible to move those JSM Projects to a non-JSM Project prior to the migration?

Ste

[Mike Gourley]

  "..move those JSM Projects to a non-JSM Project..."

Not sure I understand.  The goal is to leave the JSM project behind on the current server and move the non-JSM projects to the new server.   Do you mean change the Project Type from Service to Software before the migration and change it back again after migration?  What would that do?

[Ste Wright]

Hi @Mike Gourley 

If you're intending to leave the JSM Project as-is, I'd consider...

• Installing a JSM trial license on the destination instance
• Completing the migration
• Move the JSM Project to a JSW Project post-migration
• Removing the trial license

^ This feels like the simplest option to me.

Otherwise you're going to need a method of cloning the entire Project pre-migration. That likely requires an App, or it might be possible using Automation (to a degree...). But it feels quite a lot more complex than the option above.

Ste