Hi guys,
Custom fields are great. Thanks. But...
Sometimes it looks like you don't consider yout solution as a whole when you start updating it, resulting in more difficulty in later updates that should have been thought more properly in advance.
We should be able to associate custom fields to groups, precisely because they are Custom and may depend on the type / group of a specific project. You even place both features under the same menu (Settings)!
Does this make sense to you? I could be wrong, but I think that one of the reasons you may have different project groups and project templates is because
projects can be different, and that means that a custom field could not make sense for every project.
Project Management applies to different areas of a company. Operations projects are different from R&D or Consulting projects. If you're developing an app for this, it would be good it matches the real world.
I know it's hard and that you're doing the best you can, but this kind of structured/strategic thinking towards app design isn't rocket science. Don't take this the wrong way, I'm humbly trying to help.
Please feedback.
Thanks!