Cancel that, I guess maybe I just needed to wait a few minutes, it started working.
Comment actions
Post
Follow
Filter View Based on Toggle Custom Field - Bug?
I have created a simple toggle custom field named "micro-task" with a default value of "unchecked". Now I've added a filter to a view and set it to "Micro-Task is No" (see attached screenshot). Now all tasks that don't have the value of Micro-Task explicitly changed to Yes (On) should show up in the view, right? But in fact nothing shows up, and I find that the only way I can get any task to show up in this view is to go into a task, manually change the Micro-task toggle to Yes (On), THEN change it back to No (Off), at which point the task now shows up in the view.
This seems like a bug to me. Is it, or am I doing something wrong? If it's a bug, do you have a suggested workaround? I suppose I can use a pick list if I have to (assuming that doesn't also have a bug).
Thanks
Please sign in to leave a comment.
3 comments
Date
Votes
More on this issue, as I am still experiencing it after all. I have the filter for a view set to "micro-task is false". However many tasks for which the value is false don't show up there. I think these are all tasks that existed before I created the custom field for micro-task. I have also confirmed that if I go to one of the tasks that does not show up, change the value to true and then back to false, it then shows up in the view as it should, which I believe confirms my theory.
Would you consider this a bug (I would)? Does this apply across all custom fields? i.e. even if I set a default for the custom field and all pre-existing tasks show that default, they won't register in a view based on that filter?
Thanks
Comment actions
You are correct as the tasks that existed before the field was created did not have it and when the field was created, it may have had a value of <null> instead of FALSE. I am not certain if this is considered a bug but if you open a case and provide as much detail as possible, we will escalate to confirm if this is a bug and schedule to fix it.
Comment actions