When applying a filter based on a select/picklist field, you cannot deselect all options—despite the necessary UI elements (
, 
) showing up. Might actually be a bug? Regardless, the ability to filter tasks that have an empty/null field value would be a really valuable feature for our team.
Here’s what happens currently, when you try to remove the first/only selected value:
+1 This is a blocker for us too. It’s especially frustrating because there’s no way to assign a default for a custom field, which means it’s plainly impossible to filter to tasks with an unset value for a custom field.
In projects with 100’s of tasks, it would be valuable to be able to see only tasks with empty values in a certain columns so we can take action on those.
@Anastasia_Thomas - I’ve merged your topic with a similar request; make sure you give it a vote!
In the meantime, a workaround for this is to used the advanced search, which does have an option for filtering on null values:
Hey Stephen - I’d like to give this a vote, too, would you mind linking to that merged topic here? (With a rule that keeps not running - a bug that’s been unaddressed for over a month - that’s supposed to set a field to an option that is then used to filter/show that a task requires action, having instead the ability to filter based on a null value, that instead indicates it needs action, would be hugely helpful). TY!
@rstanley - this is the main thread for this topic (I merged other posts into here). You can use the purple “Vote” button at the top to lend your support!
Could you describe your specific issue (and/or post a screenshot of your rule builder, hiding private info)? Maybe there’s something we can modify in the meantime.
Thanks, voted. And I appreciate the offer of help here, not sure what can be done but Asana actually fixing the bug, sadly. Here’s the issue: We have a rule that trigger’s a field selection being set to a specific option based on a different field selection. The former option being set is then used to filter a view - this view is what a team uses to understand what work requests have been submitted and need immediate action. However, the rule keeps not running - which means tasks are being submitted but aren’t appearing in the ‘need action now’ view, so work is delayed and getting missed.
I thought that perhaps a workaround would be to eliminate the rule, and just have the view filtered off of ‘null’/no option selected for that particular field, but - as above - Asana doesn’t yet allow it. Ugh.
