I have custom fields where I have changed the options over time. They do not show up when I go to edit the field, but the old options show up in the filter view. No tasks (complete or incomplete) are tied to these old options. Can I get them to go away to streamline the filter?
Hi @Stephanie_Pawlush , welcome to the forum 
Thanks for posting this. Itâs something I too have also noticed the past couple of weeks and have been meaning to raise this. Indeed, previous options of custom fields show up in a project filter, however when you use advanced search and add the custom field, those options are not there.
I am going to move your post into the Report a Bug section since, I believe that, this was not the previous âexpected behaviourâ.
@Vanessa_N , could you kindly investigate this please?
In order to reproduce:
Note, this is different to the expected behaviour which, if a dropdown value is set to a task and then that value is deleted as an option from that custom field, it will still be displayed in grey and crossed out, until that value is actually cleared or changed to a currently available option.
Thanks!
Some people would find this âbugâ something very useful, so I wouldnât be surprised if it was an actual intended behaviour⊠Thatâs very useful to clean up data.
@Bastien_Siebman , agreed, but in the filter button, it displays options of which no tasks are actually set with that option. If you try to do the same with advanced search, the deleted value is not there. I would understand if it did show up there though, available to search for!
But right now, this âbugâ results in having a âdirtyâ list of options in the projectâs filter button, which is not useful when no tasks actually have that previously deleted option.
Hi everyone, thanks for tagging me here! I agree that this can be very useful to some people but very inconvenient to others. Iâve escalated this to our Developers to confirm if itâs intended and if thereâs a way to remove deleted values. As soon as I have an update Iâll share with you all 
I think the consistent behavior concerning how Asana treats other related cases would be to keep the deleted option in the filter so long as any tasks have that since-deleted value, and remove the deleted option when thatâs no longer the case.
Related: I have a practice that when I clean up a single- or multi-select custom fieldâs options, I first unset the value Iâm about to delete as an option from any tasks that use it to prevent the ghost values in tasks (unless theyâre needed historically).
Totally agree!
Hi everyone, the Developers are working on this case, but based on their ongoing discussions, this is not the intended behavior. It should be something like @lpb mentioned, with the field only appearing when tasks have the deleted value. As soon as I know more Iâll get back to you here in the thread!
Thatâs great to hear @Vanessa_N , thanks!
I am having the same issue. thank you for discussing this. Hopefully it will get resolved soon.
Hi everyone, our Developers have deployed a fix for this issue. Please refresh your Asana, and if the problem persists, let me know!
Thank you @Vanessa_N ! Confirming that this is fixed on our end. 
Thanks @Vanessa_N !
This topic was automatically closed 16 days after the last reply. New replies are no longer allowed.