this would be a very useful feature but it also looks like it could be very hard to implement

To be honest most of ours will still be location based but on certain things like for example a RAAIDD log we do have a list per task type which does each need a different set of Custom Fields - right now this is just managed in each view - but if the views were more complex this would start to become much harder.

Our main issue is actually we literally want to show different data/subtasks etc in different locations but on the same shared tasks - so we can use the same task 'Project' in mutliple places but hide/show different sets of sub tasks and data - so task type doesn't have anything to do with this.

1) Would you want to see task type and location based custom fields on tasks?

Answer: If a location has a custom field, what value does it have to the task if it's not displayed on the task (where work happens)?.. If a location has custom fields, and a task type has custom fields, I'd expect all custom fields to display on the tasks.

2) Provide specific examples if you have them --

At the moment I'm only seeing a use case for location custom fields in a "Client" folder or list, where the tasks within that location might be for different services that client is getting (digital marketing, website support, etc), but the basic client information stays the same (their website URL, point of contact, etc).

Custom fields are at the location level new, and either requires a lot of management to ensure the correct fields are being used on the new lists/folders, or moving all custom fields to the space level and encouraging our team to ignore the fields which are irrelevant.

95% Task Type.

I would like both locations to show up in the same screen, but perhaps an optional divider to mix together or show as separate groups. Similar on how one can choose between tabs or list view of details inside a Task.

Dear Ivan,

That’s a great question you are asking!

Your question 1):

In general we would prefer to only see the task type based custom fields for tasks that are set to any other task type besides “Task (default)”.

Showing both, location based and task type based custom fields, would destroy the benefit we are expecting from the new feature. Our current problem is that all tasks in a certain location are showing all of the custom fields from that location. As we are having several different task types in one location, a lot of unnecessary custom fields are shown for each task. Users are confused and do not know where to find/put information.

Our main use case is to have different custom fields for tasks that represent projects and tasks that are documents, work packages, issues, phases, ideas within a project.

----------------------

Your question 2):

No example at the moment. But I think we would use the feature to combine the custom fields from the location and the task type in some cases.

If the new feature would be implemented in this way, please have at least an option in the space/folder/list settings to choose if custom fields are combined in this location.

----------------------

The feature Custom Field based on Task Type is closely related to the request to have custom fields for folders/lists. If folders/lists would have custom fields, we would use those to represent our projects. This would allow us to calculate project progress from the tasks within the folder, for example.

----------------------

Custom fields from top level tasks should not spread down to its subtasks.

Whenever I create a new task of this type, it will come along with all your custom fields - this is the solution that best suits us.

Task Types need certain questions/data points based on the task, location like we have is true to "location". One Department needs these set of data points compared to another department needing theirs. Ours would probably be 80% Task Type and 20% Location. But need both to make my reporting needs for my location.

Today's functionality causes all the fields to meld into the task when a task is shared with other locations. Our project task types then have all the enhancement task type fields and our data is skewed because of it. I have to go in constantly to remove fields in a location that got moved because someone added a task to that location and "moved" the fields. I would love for that to be locked to "admins".

I would use both task type and location based fields. I also think custom field sharing should be an option (eg, "Client" can be relevant in different types of tasks and locations).

If we were to start over, I'd probably be a 50-50 split between types and locations. Custom fields by task types would definitely be helpful, but removing custom fields by location would mess up a lot of our lists. For example, I use dropdown custom fields quite a bit to organize and group lists. We used to use Asana, so when we migrated most of the "sections" transferred over as individual lists. I've consolidated a lot of those lists into 1 list with custom fields to group the tasks by.

Our product team heavily uses task types, so that's where it's most helpful. However, other departments like marketing and operations don't use them as much, and that's where location-based custom fields are really handy.

I'd love to see custom fields by task type, but we definitely still need them by location as well.