How to clone existing project to new jira service desk project?

[BKT Helpdesk]

Need to create new service project of same as existing. Kindly help me out.

[Kishan Sharma]

Hi @BKT Helpdesk 

Natively there is no way to clone a project in JSM. If you are not planning to make any changes in the configurations, you can create new project that shares its configuration with another project. If a change is made to one of the projects' configurations, that change affects all the projects that share that configuration. Only Jira admins can create projects with a shared configuration.

To create a project with a shared configuration:

1. Select Projects > Create project in the navigation.
2. Under project templates, templates are grouped into a series of use-case based categories. Under Products, templates are grouped by Jira Cloud products. Choose a category or product.
3. Learn more about the available templates and select a template.
4. View the detailed information on the template and choose Use template.
5. Choose project type: Company-managed.
6. Give your project a name.
7. Tick the Share settings with an existing project checkbox.
8. Use the Choose project dropdown to select the project from which you want your new project to share its configuration.
9. Select Create.

If you don't want to used shared configurations, you can simply make a copy of all the relevant schemes (issue type scheme, screens, workflows, field configuration, notifications etc) from source project and associate them to the newly created project and modify them as necessary.

[BKT Helpdesk]

For me it is showing Team managed in project type. How to change the same?

Also let me know how to clone request types with workflows from existing project to new?

[Kishan Sharma]

Jira admins can create projects from any template, including both company-managed or team-managed projects. Any user can create their own team-managed project (like the team-managed Scrum or Kanban projects). Jira admins can change this setting in global permissions. 

Unfortunately, it is not possible to copy request types to another project in JSM, you will need to recreate them manually. There's a feature request raised with Atlassian on this, please vote on this request: https://jira.atlassian.com/browse/JSDSERVER-4276 and watch it for further updates.

[Alisson hines]

Can you please guide us step by step, i am also doing this but no fortune.

[Kishan Sharma]

Hi @Alisson hines You will find steps to create a project with a shared configuration in my earlier response. Once the project is created based on another project, you will have to create the request types from scratch by referring the source project like adding the same fields, their order etc. Please inform if you require information regarding any particular step.

[Luka Hummel - codefortynine]

Hi @BKT Helpdesk

While Jira itself doesn't offer a direct “clone project” feature for team-managed projects, you could try our app Deep Clone for Jira. Deep Clone can clone team-managed projects with its Advanced Project Clone feature.

Here's how you can use it:

Steps to Clone a JSM Project Using Deep Clone

1. Install Deep Clone:
   • Go to the Atlassian Marketplace page.
   • Click on “Try it free” to start a free trial or “Buy it now” if you're ready to purchase.
   • Follow the prompts to install the app in your Jira instance.
2. Setup Advanced Project Clone.
3. Clone Your Project:
   • Once installed, navigate to the Project Clone interface via Apps > Deep Clone > Project Clone within your Jira instance.
   • Select the project you want to clone.
   • Configure the settings for the new project, including the name, key, and any specific configurations you need to carry over.
   • Initiate the cloning process. The app will handle copying workflows, issue types, screens, and other project settings to the new project.

Benefits of Using Project Clone

• Efficiency: Quickly duplicate entire projects without manually recreating each configuration.
• Consistency: Ensure that your new project maintains the same setup as the original, reducing the risk of configuration errors.
• Flexibility: Customize what aspects of the project are cloned, such as schemes, workflows, and permissions.

Additional Considerations

• Permissions: Ensure you have the necessary permissions to install apps and clone projects within your Jira instance.
• Review Configurations: After cloning, review the new project to make any necessary adjustments, especially if there are specific configurations or customizations unique to the new project's needs.