Clone Automation Caching?

[Michael Da Costa]

Hi,

I have an automation which clones tasks to a new project. This will work fine initially however Ive noticed that if i change the project which i'm cloning to then my cloning step breaks with the error:

"Can not create issue in project/issue type"

However it will work if i delete the clone step and creating a new clone step with my new project ??? Any ideas how i can get around this? 

thanks

[Trudy Claspill · Accepted solution]

Hello @Michael Da Costa 

Are you cloning issues into Team Managed projects or Company Managed projects?

[Michael Da Costa]

Hi @Trudy Claspill this is a team managed project.

[Trudy Claspill]

Issue Types have unique numeric IDs. Company Managed projects use globally defined issues types, so the Epic issue type in every Company Managed project has the same numeric ID

For Team Managed projects the Issue Types are not shared. They may have the same names, but in each Team Managed project the issue types each have a unique numeric ID.

Because of that, each time you change the destination project in the clone action you will also need to reselect the issue type you want to create. It should be enough to reselect the issue type. You should not have to delete the step entirely and recreate.

[Michael Da Costa]

Ah i see that makes sense. Thank you for the explanation @Trudy Claspill . Most helpful