Recent searches


No recent searches

Remove "NULL" values from Dashboard Filter

Not Planned


Posted Feb 04, 2020

Hi,

 

it´s right now impossible to get just a Agent list, the "ALL" can be remove but the "NULL" is always exist.

Teamleader only want to see Agent Names, not NULL without any content:

 


13

9

9 comments

Official

image avatar

Eugene Orman

Zendesk Product Manager

Hi everyone, thank you for taking the time to share your thoughts here. 

The NULL value is necessary for including or excluding values that don't have any associated value for the specific attribute. For example, tickets might not have an assignee or an organisation. While I understand that there are places where we can improve how we show and how we hide this value, there are no plans to work on this area at the moment. 

If there will be any updates in this area we will add an update on this post. 

0


If I understood your problem correctly, I think there might be a workaround. You can add another filter with the agent names and exclude the NULL, hide that filter, and create a (hidden) bookmark with this filter setting. Then you pin this bookmark so it is the state of the dashboard when it is first loaded. I haven't tried this though (just had a similar situation with other filter settings). Let me know if this works.

0


Hi Jessica,

 

this was also one of my idea, but so far I failed with it.

 

I try add a 2nd Assignee Name filter, with exclude: NULL and bookmark it, but this keep NULL still in place even with Cascade Promts.

Also creation of a "Set" with my own assigness keep Null in even when I didn´t add it to that.

 

Thanks.

0


Too bad. I agree with you then. This should be added.

0


Fully agree with this, it's really ugly and extremely frustrating that you can't remove or otherwise hide these NULL values. 

 

I can understand them being present if you're looking at a full attribute, but if I create an attribute set with only two values in it and explicitly don't select NULL to be a part of that set, there's no justification for NULL to be present when I load that set as a filter. I don't see this as a product improvement, rather this should be considered a defect in the software. 

0


This is badly needed. We share dashboard with Clients and they keep asking what the NULL is and if it can be removed.

Agree with Saxon, this is not a "nice to have", it's a defect that needs addressing.

1


Adding to this. I too have a filter with only two values in a dashboard I created for company internal use. I keep getting asked by my colleagues what this NULL is and if I can remove it. Agreeing with the comments above, this is not a "nice-to-have" feature, it's a defect of the software.

0


+1 to the post. Don't forget to upvote as that is what Zendesk looks at :)

0


+

https://support.zendesk.com/hc/en-us/articles/4411973772186-What-does-the-Null-option-mean-in-my-Explore-filter-. "Sometimes it is not useful and does not apply to the filter at all." - Yes. What is the point in null agent, when you look for agent based stats? What is the point of null organization when you look for organization based stats? What is the point of null valued channel when you look for ticket channel stats? Just to look at empty tables.

And it can not be removed. And it is always on top :) Quite an issue.

0


Please sign in to leave a comment.

Didn't find what you're looking for?

New post