Issue Cloning via Automation

[marcin_trzcinski]

I've created 2 identical projects for purpose of this exercise and i'm trying to run issue cloning from project A to B, every time when issue is created in project A.

I've red all articles i could about issue types and other dependencies but the error remains the same: "

Can not create issue in project/issue type

10159/10523"

In next steps i want to update description of issues from project A to B whenever it is changed but first of all i need cloning.

The projects are team-managed projects. Please help me to make it work!

Regards,

Marcin. 

[John Funk · Accepted solution]

Hi Marcin - Welcome to the Atlassian Community!

Issue Types (like pretty much all objects/configurations) in Team Managed projects are unique to that project by design. So Task issue type in Project A is not the same as Task issue type in Project B. They have different issue type IDs. 

So you can't do the automation using same issue type in your clone. But if you create a series of IF/ELSE statements for each issue type then it will work. 

That looks like this. If Issue Type = Task then do you clone but actually select Task as the value for the Issue type. Next grouping, If issue type = Epic, then clone to Issue Type = Epic. 

Hopefully you won't have too many of these to have to cycle through. 

Good luck!

[marcin_trzcinski]

Thank You. It worked.

[John Funk]

Great. Glad to hear.

[Luka Hummel - codefortynine]

Hi @marcin_trzcinski

If you decide that 'IF/ELSEing' through potential issue types is too much of a hassle, or you want to copy custom field values when cloning your issues, you might want to try our app Deep Clone for Jira.

Deep Clone can clone issues between different team-managed projects, and can also clone issues between team-managed and company-managed projects.