Ability to update project template association on current project

[#1]

Description - Ability to update the project template association on a project

Why is this feature important to you - We have built a lot of our content operations reporting based on the project template associate (asset type). 

How would you like the feature to work - We are currently working on a thought leadership piece that we initially thought was going to be a blog, so we leveraged out blog project template. The content has evolved and is now a full blown Viewpoint piece, which uses a different set of tasks to get to done. So, now the asset type on this piece will not appear correct in any of our content reports. 

Current Behaviour - We originally created this project: https://experience.adobe.com/#/@cgi/so:cgi-Production/workfront/project/66463d4f00258653b6af4b0d132c... originally using our Blog project template but it's now a Viewpoint. So, this Viewpoint (now) reports as a Blog, even though it's no longer a blog. We now have to create a new project and hope it doesn't cause confusion.

I had opened a case on this and told there was no solution at the moment so that is why I'm submitting this as an idea: Case #00418861.

[#2]

Hello! I'm not sure if this will help you, but we got around this problem by creating a custom field specific to "asset type" and that field is prepopulated based on the template used, but can then easily be changed if/when the direction changes. We report off of that custom field rather than the project template for this reason.

[#3]

I agree with this challenge.  Not only if you change which template is initially added but if you add multiple templates it doesn't show them.  It would be helpful to list out the actual templates used for reporting to show planned vs actual and improve the templates quarter over quarter.