Excluding Request Types from "Cloned" projects

[C_ Derek Fields]

I routinely use the "Share settings with an existing project" to create new project. I encourage my clients to create "template" projects that meet their specific business needs rather than using the available templates from Atlassian. This is because when you use an Atlassian-supplied template, it creates an entire new set of schemes and objects (e.g., workflows, screens, etc) that are identical to all of the projects of the same template. This contradicts the goal of reuse and standardization. 

The problem I have run into and would like Atlassian to consider fixing is that when I clone a Service Management project, I may not want to clone the Request Types, which tend to be specific to each project. I would like to see an option to allow me to exclude the Request Types from the new project. 

Any thoughts about this?

[Rodney Dsouza _Atlassian Certified Expert_]

It certainly is annoying to have to go delete the Request Types every time we do this "best practice".   It would nice to be able avoid this, but on the other hand it borders on "first world problem".