Hi I want to clone and ENTIRE project in Jira. Why? Because I want separated projects for iOS and Android. They will be quite similar so any suggestion please?
Below you have few possibilities:
1. You can create project using existing configuration from source project (you can choose this option while creating new project). Be aware that in this case changing for example workflow or permission scheme will affect both projects;
2. You can manually copy existing configurations like workflow, permission, boards etc. And then use it in new project.
3. If you want to copy already existing issues, components ,version etc I recommend scriptrunner and it's build-in "copy project"
4. You can also consider to stay with one project but separate Android and iOS tasks using basic jira functions like components or labels
Does the ScriptRunner 'copy project' script work with JIRA Cloud? (Looking for a plug-in solution to this problem).
No buit in script to copy project in scriptrunner cloud
Hi all ... Anyone found any route to do this? I will look at the Deep Clone add on but would like to try control this internal and possibly do this without an add on - either via the Interface or API? Anyone? Thanks in advance for new updates..
Hi @Yatish Madhav ,
It might be interesting for you that we've released an update of Deep Clone for Jira last week that enables you to clone entire Jira projects, including settings, components, versions and issues.
@Marlene Kegel - codefortynine Can you please share docs for cloning entire projects? specifically classic projects
Welcome to the community, @Khalid Alahmadi.
Sure! Here you can find our documentation about cloning projects.
If you have further questions, don't hesitate to get in touch with our support. We usually reply within one working day.
Hello,
This use case is quite interesting, as it's something I have quite often encountered when speaking with Project Managers using Jira.
Basically, what you need is a "Template" project, which contains all the possible features or specs that will need to be often reused. This is your source of truth, that needs to always be up-to-date and will be copy, partially, each time a new project is created. In this example, you will pick and select issues (or Epics) for the iOS project, and pick and select other issues (or Epics) for the Android projects. There will be overlap, potentially a lot of overlap, between the content of the two projects.
To do this, what I would advice is to have your template project organized in Epics, with issues and subtasks within. When a new project is created, you should simply select the Epics that suit the project, and bulk clone them while keeping their hierarchies.
This can be done with our add-on, Elements Copy & Sync.
It will let you bulk copy issues from the Jira search results (here, the Epics you are interested in) while automatically retrieve their issues (using the Jira Epic clone feature).
What is particularly interesting is that the app lets you keep your projects synchronized. This is useful when your "source of truth" needs to be updated. You will be able to simply update the stories in the template project, and the changes can be automatically applied to all the projects that were created from it.
The app is free for 30 days, (and stays free if your instance is under 10 users), so feel free to give it a try, and don't hesitate to tell reach our Support if you have any question.
Kind regards,
Julien
Hello Julien,
Does Elements Copy & Sync also clone config's, workflows and scripts from one project to another?
Hello @carl
No, Elements Copy & Sync is meant to copy issues, with everything in them (fields, comments, attachments, etc.).
However, when creating a Project with Jira, I do believe there is a native option to create this Project from another one, thus copying its config, workflow...
I hope this helps.
It looks like you're new here. Sign in or register to get started.
