How do I best move tickets across one project to another similar project?

[Simon Hedges]

I need to move tickets from a Jira project on one server, across an air gap to a Jira project on another.  The destination project has the same fields, priorities, statuses, resolutions, etc as the source one (though the internal IDs are different), but the user IDs are different, and so are the Sprint IDs. 

Does Jira help with any of this?  I'm particularly concerned about the Sprints not going across.

[Blue Ridge Consultants · Accepted solution]

Hey Simon,

I'd recommend taking a look at Configuration Manager for Jira.  I've been using the tool for use cases just like this for years.  The support and documentation for this app are amazing.

https://marketplace.atlassian.com/apps/1211611/configuration-manager-for-jira-cmj?tab=overview&hosting=cloud

[Simon Hedges]

Thank you.  Unfortunately the system I am moving from is Jira Server without this app, and Atlassian will no longer sell this app (and we are moving to a new instance so won't upgrade), so this isn't an option for us.

[Joe Pitt · Accepted solution]

Jira doesn't support this out of the box. There is a plugin in the marketplace to move projects. I don't know if it will do that, but look in the marketplace.

[Simon Hedges]

Thank.  Unfortunately as a dying instance that won't upgrade from Server to DataCenter, we're not allowed to buy any more apps, even if those apps help us migrate to a DataCenter instance of Jira (thanks Atlassian!).

But thanks for the confirmation that Jira doesn't support this out of the box.