Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

I want to copy all the Issues from JIRA service management to JIRA Software, and not move it.

Pooja Sree August 22, 2023

I want to copy all the Issues from JIRA service management to JIRA Software, and not move it. All the videos and comments showed me ways to move the issues, but i just want to copy those to the JIRA software project. 

Can i do this by cloning the Queues? 

3 answers

1 vote
Trudy Claspill
Community Champion
August 22, 2023

Hello @Pooja Sree 

Welcome to the Atlassian community.

Through the UI you can clone issues one at a time into the same project, and then move the clones to another project.

Or you can create an Automation Rule and use the Clone Issue action in the rule to clone the issues to a different project.

https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Clone-issue

Pooja Sree August 22, 2023

@Trudy Claspill Thankyou for your prompt reply.

Pooja Sree August 22, 2023

@Trudy Claspill I have tried the Clone Automation, but it doesn't  work. Is there any other way i can copy the issues to JIRA software project, without effecting any issue in Service Desk?

Trudy Claspill
Community Champion
August 22, 2023

If you want help debugging a rule you will need to show us all the details of the rule, the details of the Audit Log for an execution of the rule, and explain to us what you are observing when you say it "doesn't work".

Is this a one time need or something that will need to be repeated?

Do you want to keep the issues in the Software project synchronized with changes in the Service Management project, or have them updated independently?

Note that even with Cloning not all information will be copied from the original issue to the new issue. If there are fields used in the Service Management issues that don't exist in the Software issues, that information won't be copied. Comments don't get copied. Issue links don't get copied. Issue history doesn't get copied. And the issue will be put into the first Status that is valid for the Workflow for issues in the Software project.

Another alternative is to export the issue data to CSV and then create issues in the Software project by importing the CSV. Through a CSV import you can "clone" comments and recreate issue links.

You might also look at third party apps from the Atlassian Marketplace that provide more extensive issue cloning functionality.

0 votes
Thibaut Subra _Elements_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 28, 2023

Hello @Pooja Sree 

Your need seems to require special rules and tools.

I suggest to take a look at our Copy and Sync application that allows you to copy several issues in bulk, with all the content you need (summary, description, attachments, comments, custom fields, etc.).

Everything can be easily configured in a recipe that you can trigger from the advanced search for instance, or even from an Automation rule.

Capture d’écran 2023-08-28 à 15.19.59.png

Let me know if you have any question.

Our app is free under 10 users and we have a 30-Day trial policy.

Regards!

Thibaut

0 votes
Luka Hummel - codefortynine
Atlassian Partner
August 23, 2023

Hi @Pooja Sree

If you are willing to try a third party-app, our Deep Clone for Jira can help you copy your issues to another project.

With its Bulk Clone feature, you can just select the source project and copy all its issues to the target project. Here is a detailed guide on how to facilitate this.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events