Hide Ticket Attributes to Declutter Filters and Improve Performance
Speed up edit mode and simplify your filters lightbox by hiding static attributes you no longer use.
Why Hide Attributes?
Every static attribute (ticket field) in your account is loaded into the filters lightbox whenever you open it — and whenever you enter edit mode on a dashboard. If your Zendesk instance has dozens of dropdown fields that come over in the webhook payload, many of which your team no longer actively filters on, all of those fields still load every time.
By hiding attributes you don't need, you can:
Improve load time — The filters lightbox and edit mode only load the attributes that are visible, so fewer attributes means faster performance.
Declutter the UI — Your filter list becomes shorter and easier to scan, making it faster to find the attributes you actually use.
Reduce noise — Team members won't accidentally filter on outdated or irrelevant fields.
Note: Hiding an attribute does not delete it or disable it. The attribute and its data remain fully intact. It is simply hidden from the UI in places like the filters lightbox. You can show it again at any time.
How to Hide Attributes
In the left-hand navigation, go to Objects → Static Attributes, or navigate directly to qvasa.com/objects/static_attributes.
You will see a table listing all of your static attributes. Look for the "Hide/Show in UI" column on the right side of the table.
For each attribute you want to hide, click the "Toggle Visibility" button in that row.
The attribute's visibility status will update immediately. Hidden attributes will no longer appear in the filters lightbox or in edit mode.
How to Show a Hidden Attribute Again
If you need to bring back a hidden attribute, simply return to Objects → Static Attributes and click the "Toggle Visibility" button again for that attribute. It will reappear in the filters lightbox and edit mode immediately.
Tips for Choosing What to Hide
Start with unused Zendesk dropdown fields. Many accounts have legacy ticket fields that were created for old workflows or integrations. If nobody on your team filters by them, they are safe to hide.
Check with your team first. Before hiding an attribute, confirm that no one is relying on it for their dashboard filters or reports.
Hide in batches. Go through the full list and hide everything you don't need in one pass. The more you hide, the bigger the performance improvement.
You can always undo it. Since hiding is fully reversible, don't be afraid to hide aggressively. If someone needs an attribute back, it takes one click to restore.
FAQ
Will hiding an attribute delete any data?
No. Hiding an attribute only removes it from the UI (filters lightbox, edit mode). All underlying data is preserved. Tickets that have values for that attribute are unaffected.
Does hiding an attribute affect existing dashboard filters?
No. Any dashboard that already has a saved filter using a hidden attribute will continue to work as expected. The attribute is only hidden from the filter selection UI, not from already-configured filters.
Why is edit mode slow?
When you enter edit mode on a dashboard, Qvasa loads the filters lightbox which includes all visible static attributes. If your account has a large number of Zendesk dropdown fields, this can take several seconds. Hiding attributes you don't use is the most effective way to speed this up.
Who can hide and show attributes?
Any user with access to the Objects → Static Attributes page can toggle attribute visibility. Check with your account admin if you do not see this page in your navigation.