I would like to Move / Copy / Clone issues from one jira instance to another to archive issues.
anyone know how we could move issues based on a JQL filter to another instance?
I'd recommend you using Configuration Manager for Jira for this one - the add-on gives you the ability to copy, clone or move Jira project configurations between instances, including their issue data. For migration purposes, it is known to deliver with zero data loss.
Here are some of the use cases that are relevant to your scenario:
If you have any questions, ping me :)
I would highly encourage you to look at managing this with permission schemes. You can easily make issues "Read-only" and restrict most everyone from seeing them. The reason that I suggest this way is because splitting JIRA instances is normally not an easy task. There is often quite a bit of overhead. If you have to go down the splitting route for some reason, there are basically two options.
1) Use the project export/import feature. Export a project from one JIRA instance and import it into another. The reason this is difficult is because the configurations between the two projects need to be essentially identical. This can require quite a bit of work to make them match. Additionally, you can only import into an empty project. This means you cannot import new issues that you want archived into an existing archive project. Unless you were able to leverage project templates, this method will require a lot of overhead. You may be able to reduce some of this configuration work with a plugin.
2) I do not have any affiliation with, nor have I used this plugin, but there does exist a plugin that can copy issues between remote instances. One issue with this is that Atlassian Labs makes it, it is unsupported, and not compatible with the latest versions.
In general, this really is a chore to accomplish. Unless you've got no other option, I personally wouldn't go down that route.
Hope this helps.
To contribute to Kian, this is the plugin he may have had in mind -- https://marketplace.atlassian.com/plugins/com.awnaba.projectconfigurator.projectconfigurator/server/overview
It can do the work for you on it's own - but I recommend reading through the documentation first to really know what it does and how - it's powerful, so handle with care.
Though, I'm curious why you'd want to do a migration to archive data this way, there're backups for this.
I agree with Kian that the Project Import from a backup file is a headache.
Exporting issues to CSV from the issue navigator and importing them to the target instance seems to be a better option.
However, I would personally go for an offline archival approach, exporting issues to all formats at your disposal (CSV, HTML, Word, PDF, XML...) together with their attachments, and keep all that stuff properly classified in a folder anywhere else (Google Drive, Dropbox...).
That way, the info would be available for further consultation but not subject to licensing limitations, plus you avoid the temptation of resurrecting the project with its former configuration, which can take more effort than building it from scratch, specially as requirements change over time.
Don't be afraid of 'loosing' settings or searching capabilities: The exact configuration doesn't matter in read only mode, and Ctrl+F or Google Search is just good enough.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs