Custom fields - Applied to levels
It would be good if we could have custom fields to be only applied to Task Item types. Currently to have a custom field in a task it also needs to be at project level which isn't that helpful.
A task will have far more items than what is needed at the parent project level.
Scott McKinley not sure how much experience you have with Custom Item Types, but you can show or hide any fields in the project item type vs the task items type. I think where your idea would be best used is in the new table view. It would be nice to have fields/rows not applicable to the project be greyed out, and the same for tasks if a project CF is not applicable.
I have quite a bit. The problem is that if you use a custom item type in a space where custom fields are applied you can't hide all fields via the custom item type designer, as it's a hierarchy and so are fed down.
I'll share your feedback with the team Scott McKinley 👍
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
Upvoting and second this, but I will also raise that it should be restricted down to the Custom Item Type level. While you can determine which fields are on which item type, in a table view, they are all there. If you have two custom item types built from a "project" on the same table view, but your custom field only applies to one of those custom Items of type "project", a user can fill the field in for both when really it is only applicable to one.