nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

best way to recreate issues and subtasks to another project

Anca Cristescu

Hello,

We have to create a new project definition for our development process, with new issue types, workflows....

We have to move/copy/clone the issues that are still in the old project to the new one, but they have a totally different structure:

Before:

task + subtask (and subtasks were differentiated by 'activity')

Now:

software problem + 5 types of subtasks

We try to use Clone+ for Jira to clone this issues... but it works ok for task, but not for our subtasks ...

Does anyone have any recommendations?

Accepted answers

Marc -Devoteam-

Hi @Anca Cristescu

This KB article should provide you with the content you need, this is based on Jira Automation

https://support.atlassian.com/automation/kb/writing-a-rule-that-clones-stories-and-their-sub-tasks-when-epic-is-cloned/

Or check the apps:

Deep Clone
Elements Copy & Sync

Clara Belin-Brosseau_Elevatic

Hello @Anca Cristescu

And thank you @Marc -Devoteam- for mentioning Elements Copy & Sync!

If I understand correctly, you’re trying to clone issues from a project to another one with different issue types, right?

In that case, I would recommend trying our app Elements Copy & Sync that allows you to clone and sync a full hierarchy of issues with all their content (summary, description, custom fields, comments, attachments, etc).

You’ll be able to clone all the issues at once and map the different issue types from the old to the new project.

You can check the guide here.

The app is for free during 30 days (and it stays free under 10 users).

All comments

Marc -Devoteam-

Hi @Anca Cristescu

This KB article should provide you with the content you need, this is based on Jira Automation

https://support.atlassian.com/automation/kb/writing-a-rule-that-clones-stories-and-their-sub-tasks-when-epic-is-cloned/

Or check the apps:

Deep Clone
Elements Copy & Sync

Clara Belin-Brosseau_Elevatic

Hello @Anca Cristescu

And thank you @Marc -Devoteam- for mentioning Elements Copy & Sync!

If I understand correctly, you’re trying to clone issues from a project to another one with different issue types, right?

You’ll be able to clone all the issues at once and map the different issue types from the old to the new project.

You can check the guide here.

The app is for free during 30 days (and it stays free under 10 users).

Anca Cristescu

Thank you both for your quick reply :-)

I'll test Elements Connect and see how this works for us. We are DC so we can't use Deep Clone.

Clara Belin-Brosseau_Elevatic

My pleasure @Anca Cristescu

Be careful to use Elements Copy and Sync and not Elements Connect which is another of our apps but doesn't serve the same purpose

Anca Cristescu

Yes

We have Elements Connect also, and I wrote it by habit

Clara Belin-Brosseau_Elevatic

Ahah great

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server

jira-data-center

clone

data-center