product-example checked
Zendesk Creating views to build customized lists of tickets
Documents ticket views as personal or shared lists built from condition statements, with access settings, previewing, columns, cloning, and limitations on available condition fields.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Saved filter | Choose saved filter when users need to preserve and reapply a named set of filter values, operators, and fields across sessions. | Saving stores filter criteria definitions, not the current result IDs. | Zendesk documents ticket views as condition-based personal or shared lists with access settings and preview behavior. |
| Saved view | Choose saved view when users need to persist a named combination of layout, columns, grouping, filters, sort, density, and other display preferences for a data surface. | Saving stores a canonical view definition, not a static list of current row IDs. | Zendesk documents ticket views as personal or shared lists with condition statements, access settings, preview, columns, and cloning. |
Evidence Role
This source is treated as product-example evidence. Use it to validate the decision rules above, not as a visual style reference.
Publisher: Zendesk Help. Last checked: .