Our setup is this:

Location to create a task = various lists (each client has a project list)

If relevant for another department -> task is added manually to the department's list (one list)

Problem:

The second list (the department specific list) contains custom fields that the original lists do not (which is on purpose), so when creating a task from a template which used both lists' custom fields the template would try to add these custom field definitions to the original list, which is not intended.

Feature Request:

The task template should allow to set secondary lists a task is always added to right when the task is created from the template.

Considerations:

Automations can sort this to a certain point, but only via templates the correct custom field choice can be made when a human decision needs to be made.