How I can value-basec clone a project

[c_ermeier]

Hello,

How I can value-basec clone a project within all settings, Issues in as the same status as in the master project?

Best regards

C. Ermeier

[Luka Hummel - codefortynine]

Hi @c_ermeier

If you're looking to clone a Jira project while preserving all its settings and keeping issues in the same status as in the master project, and you are willing to try a third-party app, our app Deep Clone for Jira can help you.

With Deep Clone, you can:

• Clone an entire Jira project with all settings, versions, components, and boards.
• Retain issue status in the cloned project (provided the target workflow supports the required statuses).
• Clone all issues while keeping comments, attachments, and links.
• Bulk clone issues for large-scale migrations or project duplication.
• Clone to another Jira instance, if needed.

To maintain issue statuses during cloning, ensure that the workflow in the target project supports the required statuses. Deep Clone will attempt to preserve the issue statuses as long as the workflow conditions allow.

[Clara Belin-Brosseau_Elements]

Hi @c_ermeier,

Cloning an entire project in Jira, including its configuration and issues, can be achieved through a combination of native Jira features and the Elements Copy & Sync app.

 Here's how you can proceed:

1. Clone project configuration

Jira provides a native option to replicate a project's configuration:

• Create a new project: Navigate to Projects > Create project.
• Share settings: During setup, select the "Share settings with an existing project" option. This will duplicate workflows, permissions, and issue type schemes from the source project to the new one.

Note: The Jira native feature clones only the project's configuration, not its data.

2. Clone project issues

To duplicate all issues, including their hierarchy and associated data, consider using our app Elements Copy & Sync:

• Bulk clone issues: Elements Copy & Sync allows you to clone multiple issues simultaneously, preserving their structure and relationships.
• Clone epics with child issues: Easily duplicate epics along with all associated stories and subtasks.
• Copy attachments and comments: Ensure that all relevant data, such as attachments, comments, labels, and custom fields, are included in the cloned issues.
• Cross-instance cloning: The app supports cloning projects across different Jira instances, facilitating broader organizational needs.

I recommend you to check this step-by-step guide on how to clone a project in Jira (both its configuration and data).

You can try Elements Copy & Sync for free for 30-day free trial (it remains free for instances with under 10 users).

Let me know if you have any further questions or need assistance with the setup!

[Jack Brickey]

Hi @c_ermeier , that isn't currently available. OOTB. There are third-party solutions such as deep clone for Jira that you could look into. Check out the marketplace for possible options if that is an option for you. Most if not all apps allow for free trial.

[Jack Brickey]

Note - you could use CSV export/import to copy issues to a new project but not configuration data.

[c_ermeier]

Thanks! I saw this options.

CSV export/import works not in free Plans. I'm right?

[Jack Brickey]

It works in free.