I have mentioned this already mulitple times to succes managers from Autodeks, but it doesnt seem te get through.
Why are things developed for projects instead of project templates. Basicaly a template is also a project, but one that gets copied when a new project is created based on that template.
For instance, we now have "Correspondence". And for that types of correspondence can be configured... ONLY FOR PROJECTS! Which means we have to configure that for each project all over again.
Templates are there to help us standardize projects. And these kind of things (types of correspondence) is a important thing you want to have standardized. We do over 200 projects a year, use (currently) 4 types of correspondence (which would be more if we could use it in a template). Which means the lady that creates the projects has to create 800 correspondence types, where only 4 were needed in case of having it in a template.
This is just an example, there are multimple things that need to be configured per project instead of per template. It's a real shame. It's low hanging fruit to improve the product and make it user friendly. To make it easier to work with.
Also, it seems that once it's developed for projects, there is no interest to expand it to templates (there are ofcourse a lot more exiting new things to invent instead of making the product nicer to work with).
Making things that can be configured in a project also available in a template is the missing link. It's the thing that would make a nice product a great product.
