Apply Custom Fields Only to Top Level Projects

Currently, when you make a custom field, the only three options all involve applying the custom field into descending projects.  Would love an option to only apply the custom field to that specific project's level. We have a project structure where we want to be able to "tag" certain projects underneath another project without copying the top level project's custom fields down.  

E.g. We have "A" Projects, and we need them to be projects to allow for reporting.  But there are B and C sub-projects that need to rest inside A projects.  The custom fields we assign to A type projects are not relevant to B and C type projects, but as soon as we tag B and C type projects inside an A project, the custom fields pop up in list view for the B and C projects. 

Upvote 10
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
1 comentario

Better yet, the ability to assign custom fields to specific custom item types.  Each "level" of project can be a custom item based off of a project type and named according to its role in the hierarchy.  You can then hide or reveal specific custom fields, etc. for the custom items, but this would only apply to the detail/info view of that item.

However, there is always the possibility that if two custom "project" items are nested on the same table-type view, those fields will be exposed and can be filled in when they should not be.  Assigning fields to a custom item will prevent mistaken entry into the non-applicable fields.

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Folllowing List for Post: Apply Custom Fields Only to Top Level Projects
[this list is visible for admins and agents only]

Arriba
Didn’t find what you were looking for? Write new post