Step 1: Create a task template containing two custom fields "Product Team" dropdown and "Status" dropdown. Set "Status" to OPEN in the template

Step 2: Create a list view with the filter "Product Team" = BACKEND

Step 3: Create a new task with the template applied in the filtered list

Expected Behavior: The template instantiates with the "Status" value of OPEN and also applies the "Product Team" value of BACKEND from the filter.

Actual Behavior: The filter value of "Product Team" BACKEND is applying first and then the template is instantiating and overwriting this field so we are left with only the template custom field value "Status" of OPEN

As a workaround, I've stopped importing the custom fields with my template so it will properly inherit the filter value, and I'm using automation to populate the status. I think you should consider either changing the order of operations here (apply template then apply filter) or allow users to define which custom fields to import when applying a template.

THANKS!