Backbone Issue Sync for JIRA might be a good fit for that use case.
Using Backbone, you can keep multiple projects (either within the same JIRA instance, or with another JIRA instance) in sync. Once you change something in the project, it will automatically be synced to the other project (if defined so in your configuration).
You can find more information about Backbone on our website: https://www.k15t.com/software/backbone-issue-sync
We'll also have a free webinar about Backbone later this day, please feel free to register: https://www.k15t.com/blog/2016/06/backbone-issue-sync-for-jira-two-webinars-on-june-15th (if you can't make it, please feel free to register nevertheless, as we'll send out the recording after the webinar to all registrants).
I hope that information helps - of course we're also happy to answer specific questions directly, please feel free to reach out to me and I'll be happy to help: email@example.com
Hi Nils, thanks for the information. My requirement is to copy the existing issues from two different projects (with two different project key) into one target project (with different project key) without losing any data, link, or attachment. Since the project key will change to the issues in target project after cloning, thought of keeping the old key values in a custom field on the issues prior to clone.
I knew JIRA allows to copy or clone from one project to other, but I doubt it has done a great job of doing that so far with custom fields. But your product may help for ER and will try it out. Thanks again.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot