I know I cannot clone a next-gen project but...

[sherri_nc]

I am aware of the limitation around cloning next-gen projects in an automated fashion.  However, that does not change the fact that I need to do this by any means possible.  Does anybody know what things that I need to look out for when I am doing this manually?  I don't want to mess up the manual clones by forgetting some hidden key setting.  We have automation that depends on the project configuration.  I need to end up with an exact copy of the original project - aside from the project key.

Thanks!

[Trudy Claspill]

How far do you have to go in this "exact clone"? Custom fields will be considered unique to each project and will not have the same Custom Field ID, for example.

And, once created, any user assigned to the Administrator role will be able to modify the project configuration so that the projects may no longer have identical configurations.

You would need to look at all the fields and make sure they are configured identically. In workflows you need to look at the Rules associated with the transitions. You will need to look at Quick Filters associated with Boards. You'll need to check the issue types, and all of the above for each issue type.

Why do you need to create exact copies of Team Managed projects? If you need to have projects that have identical configurations, why not just use Company Managed projects so that you can share the configurations between projects?