product-example 2 linked patterns 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.

Read with a purpose

What this source can teach

Use this source to inspect a concrete implementation and the decisions visible in its context.

  1. Start with the original. Open the source and find the guidance or example relevant to your task.
  2. Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
  3. Check the setting. Compare the source's platform, people, and constraints with your own decision.

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.

Comparisons supported by this source

Evidence Role

This source is treated as product-example evidence. Its value comes from the specific claims and setting described above.

Publisher: Zendesk Help. Last checked: .

Saved items