Using views to manage ticket workflow Follow

team professional enterprise plans

Views are a way to organize your tickets by grouping them into lists based on certain criteria. For example, you can create a view for unsolved tickets that are assigned to you, a view for new tickets that need to be triaged, or a view for pending tickets that are awaiting response. Using views can help you determine what tickets need attention from you or your team and plan accordingly.

Many support teams use views to guide the workflow by requiring agents to address tickets in one view first and then others in a specific order. Views can also mirror the support structure you've created. For example, if you provide different levels of service for different customers or manage escalation using a tiered support group structure (Level 1, Level 2), you can create views for each of these scenarios.

Zendesk Support includes some default views. You can also create new custom views. Agents can create personal views for their own use, and administrators can create shared views accessible to all users or groups of users.

All views, including those currently without tickets, appear in the Views list, located on the left side of the Agent Dashboard when you click the Views icon () in the sidebar.

Note: On Essential you have default views only. You cannot modify default views and you cannot create custom views.

This article covers the following topics:

Adding views

Agents can create views for their own personal use. Administrators can create personal views, as well as shared views for use by multiple agents.

Community tip! Graeme shares real-world best practices for setting up and using views in this community tip, Views best practices.

To add a view
  1. Click the Admin icon () in the sidebar, then select Views.
  2. If you're creating a personal view, select the Personal tab.
  3. Click Add view.
  4. Add the conditions to define this collection of tickets (see Building view condition statements below).
  5. You can test the conditions by selecting Preview match for the conditions above.
  6. Set the formatting options (see Setting formatting options below).
  7. Set the view's availability (see Setting a view's availability below).
  8. Click Create view.
    Note: You cannot create more than 12 shared and eight personal views.

Views can also be managed (edited, deactivated, and so on) in the Views page.

Watch this short video for instructions on creating a personal view:

Creating a View (01:19)

Building view condition statements

As with the other business rules, you select collections of tickets using conditions, operators, and values.
Note: You must have at least one of the following ticket properties in the Meet all of the following conditions section: Status, Type, Group, Assignee, or Requester. Some conditions may not be available, depending on your plan.
Table 1. View conditions
Condition Description
Ticket: Status The ticket status values are:
  • New
  • Open
  • Pending
  • On-hold
  • Solved
  • Closed

When selecting a status, you can use the field operators to specify a range of tickets based on their status. For example, a condition statement that returns only New, Open, and Pending tickets looks like this: Status is less than Solved.

For more information on these status values, see Ticket status basics.

Ticket: Form Select the required ticket form.

For more information on ticket forms, see Creating ticket forms to support multiple request types.

Ticket: Type

The ticket type values are:

  • Question, the most common ticket type.
  • Incident, which indicates that there is more than one occurrence of the same problem
  • Problem, a support issue that needs to be resolved.
  • Task, used by the support agents to track various tasks.
Ticket: Priority The ticket priority values are:
  • Low
  • Normal
  • High
  • Urgent

As with ticket status, you can use field operators to select tickets that span different priority settings. For example, this statement returns all tickets that are not urgent: Priority is less than Urgent.

Ticket: Group The ticket group values are:  
  • (—), which indicates that no group is assigned to the ticket.
  • (current user's groups), which includes all the groups to which the agent who is updating the ticket belongs.
  • (assigned group), the group assigned to the ticket.
  • Group name, the name of the group that is assigned to the ticket.

Group name is the actual name of the group that is assigned to the ticket.

Ticket: Assignee

The ticket assignee values are:

  • (current user), the last person to have updated the ticket.
  • (requester), the ticket requester. You can select this option to return tickets that were opened by and then assigned to the same agent, for example.
  • (assignee), the person who is assigned to the ticket.
  • Agent name, the name of the person assigned to the ticket.
Ticket: Requester

The ticket requester values are:

  • (current user), the last person to have updated the ticket.
  • (requester), the ticket requester.
  • (assignee), the person who is assigned to the ticket. The condition statement ‘Requester is Assignee’ is true if the requester is also the person assigned to the ticket. This is possible if an agent created a ticket and was then assigned to it.
  • Agent name, the name of the agent assigned to the ticket.
Ticket: Organization

The organization values are:

  • (—), which indicates that no organization has been added to the ticket. 
  • Organization name.
Ticket: Tags

You use this condition to determine if tickets contain a specific tag or tags. You can include or exclude tags in the condition statement by using the operators Contains at least one of the following or Contains none of the following. More than one tag can be entered. They must be separated with a space.

Ticket: Description The description is the first comment in the ticket. It does not include the text from the subject line of the ticket.
Ticket: Channel

The ticket channel is where and how the ticket was created and can be any of the following:

  • Web form
  • Email
  • Chat
  • Twitter
  • Twitter DM (direct message)
  • Twitter Like
  • Voicemail
  • Phone call (incoming)
  • Phone call (outgoing)
  • Get Satisfaction
  • Feedback Tab
  • Web Widget
  • Mobile SDK
  • Mobile
  • Help Center post
  • Web service (API)
  • Trigger or automation
  • Forum topic
  • Closed ticket
  • Ticket sharing
  • Facebook Post
  • Facebook Private Message
  • Satisfaction Prediction
Ticket: Received at This condition checks the email address from which the ticket was received. The ticket can be received from a Zendesk email domain such as, or from an external email domain such as The external email domain must be set up as described in Forwarding your incoming support email to Zendesk or the condition won't work.
Ticket: Satisfaction This condition returns the following customer satisfaction rating values:
  • Unoffered, which means that the survey has not previously been sent
  • Offered, which means that the survey has already been sent
  • Bad, which means that the ticket has received a negative rating
  • Good, which means that the ticket has received a positive rating
    Note: In order to select this condition, customer satisfaction must be enabled. See Using customer satisfaction ratings for more information.
Hours since... This condition allows you to select tickets based on the hours that have passed since the ticket was updated in the following ways:
  • Hours since created
  • Hours since open
  • Hours since pending
  • Hours since on-hold
  • Hours since solved
  • Hours since closed
  • Hours since assigned
  • Hours since update
  • Hours since requester update
  • Hours since assignee update
  • Hours since last SLA breach
  • Hours until next SLA breach
  • Hours since due date (for tickets with the type set to Task)
  • Hours until due date (for tickets with the type set to Task)
    Note: If you are on Enterprise and have multiple schedules, views based on business hours will use your default schedule (that is, the first schedule in your schedules list). In a upcoming release, this will change so that views will use the schedule that is applied to the ticket.
Ticket: Custom fields Custom fields that set tags (drop-down list and checkbox) are available as conditions. You can select the drop-down list values and Yes or No for checkboxes.
Note: Each custom checkbox field must have an associated tag. Otherwise, when you create or edit a view, it will not appear as an available condition.
Requester: Language Returns the language preference of the person who submitted the request.
Ticket sharing: Sent to Checks whether a ticket was shared to another Zendesk Support account via a specific ticket sharing agreement
Ticket sharing: Received from Checks whether a ticket was shared from another Zendesk Support account via a specific ticket sharing agreement

Setting formatting options

You can decide what ticket data you want displayed in a view, how the tickets are grouped and ordered, and how many tickets are shown per page. Theres is a List style view and a Table style view. To select the ticket data you want included in the view
  1. Select the Table formatting option.
  2. Drag the table columns you want to include and drop them into Columns included in table.

    You can add up to nine columns. Status is always included in the table; you do not have to manually add it.


To set the order of a view
  • Select the ticket data field you want to use as the default data to order the tickets in the view. You can select Ascending or Descending.

To set the grouping of tickets in a view
  • Select the ticket data field you want to group the tickets in the view. You can select Ascending or Descending.

Setting the view's availability (administrators only)

When an administrator creates a view, they have the option of setting who can access the view. They can create a shared view, available to all agents, or they can create a personal view.

Professional and Enterprise administrators have the additional option of creating a shared view that's limited to a specific group.

Note: The Agents in group option is only available for Professional and Enterprise.

Editing and cloning views

You can edit and clone views. Cloning a view creates a copy that you can modify and use for some other purpose.

To edit a view
  1. Click the Views icon () in the sidebar, then select a view.
  2. Click the View options menu in the upper right.

  3. Click Edit. The View edit page is displayed and you can modify the view as needed.
To clone a view
  1. Click the Views icon () in the sidebar, then select a view.
  2. Click the down arrow next to the title of the view.

  3. Click Clone. A copy of the view is displayed in the View edit page, and you can modify the cloned view as needed.

Sharing views

You can share a permanent link to a view in emails or web pages. Normal access permissions apply to the users who click the link. See Setting the view's availability. Agents can only share personal views.

To share a link to a view

  1. Select Manage > Views.
  2. If you're sharing a personal view, select the Personal tab.
  3. Locate the view you want to share and select Edit.
  4. Copy the permanent link in the upper-right side and use it in an email or a web page.

Reordering views

If you want certain views you use frequently to appear higher on the list, you can adjust the list order. Agents can reorder only personal views, while administrators can reorder both shared and personal views.

To reorder your views

  1. Click the Admin icon () in the sidebar, then select Views.
  2. Select Shared or Personal from the drop-down list above your views.
  3. Next to the sorting icon, click the ... button.

  4. Select Reorder page.
  5. Click and drag the names of views to adjust the order.
  6. Click Save when finished.

Deleting and deactivating views

If you decide that you no longer need a view you can either delete it or deactivate it. Deleting it of course means that it's gone and can't be retrieved. You can instead deactivate views. Deactivated views are listed in a separate table on the Views page and can be reactivated if needed.

To delete a view
  1. Click the Admin icon () in the sidebar, then select Views.


  2. If you're deleting a personal view, select the Personal tab.
  3. Locate the view you want to delete and select Edit.
  4. Click Delete next to Submit.
To deactivate/activate a view
  1. Click the Admin icon () in the sidebar, then select Views.


  2. If you're deactivating a personal view, select the Personal tab.
  3. Locate the view you want to deactivate and select Deactivate. This command appears when you move your mouse over the view in the list of views.
  4. Click OK to confirm that you want to deactivate the view. The view is deactivated and displayed in the list of inactive views.
  5. To reactivate the view, select it from the list of inactive views and select Activate.

Exporting a view to a CSV file

You can export a view to a comma separated values (CSV) file. The CSV file will contain an entry for each ticket and all its associated ticket information in the view.
Note: Because of the processing involved in generating a CSV file, you can export a view only once every 10 minutes. If there is less than 10 minutes between requests, you will receive an error message.

Community tip! Check out Serge's community tip for exporting views in our Community.

To export a view to a CSV file
  1. Click the Views icon () in the sidebar, then select a view.
  2. Click the View options menu in the upper right.

  3. Click Export as CSV.

    You will receive an email notification (sent to your primary email account in your user profile) that contains a download link for your CSV file.

Have more questions? Submit a request


  • 0

    Thanks Anton!

    I really like the Ticket Views Widget because I am looking for a multi-view display on one page.

    I'm wondering if there is a way to expand this widget to show the tickets too?

    Or possibly a page that has multiple views on it? I mean "All unsolved tickets" & "All unassigned tickets" on the same page?

  • 0

    @Benjamin While the 'Ticket Views' widget currently only shows you the number of tickets in each view, the default 'Unassigned Tickets' view will display tickets that are both unassigned and unsolved. Is that what you had in mind? If not, could you clarify what you mean by a page with multiple views on it? If you select the 'more' link from your 'Views' drop-down menu, you will see all of your views on the same page. 

  • 0

    Hi Jill! I have attached the end goal, I made it with photo editing software.

    When I select(Image) my drop down 'Views' tab, there is no 'More' link. The link is not in the 'Inactive Views' list either. Am I looking in the wrong place?

  • 0

    @Benjamin Thanks for sending the screenshot. Since you only have 3 active views, the 'more' link is not appearing in your 'Views' drop-down. Once you have more than 13 active views, the 'more' link will appear in your drop-down so that you can access your other views that are not displayed. If you still have questions about how your views appear, please let us know and we'll create a ticket on your behalf - you can also email us at

  • 0

    Sorry, I should clarify my request. I posted my end goal, not an actual screenshot.

    Maybe a change of terms would help, I am trying to put multiple 'views'(tables or lists) consolidated on to one page.

    The following images should help. Screenshot is what I have and Goal is of course my goal. Has no one requested this before?

    Thank you for your patience Jill.

  • 0

    Hi Benjamin,

    We don't currently have ability to display multiple views on one page.  The reasoning for this is that views can grow to have 15-30 tickets per page, and putting multiple views on one page would make them difficult to view.  You may want to consider creating custom views that allow you to see the types of tickets that you'd like to see in one view.  (For example, a view that showed all the tickets from two groups, or a view that showed tickets in new, open, and pending statuses.)

    feel free to reach out to us at if you have specific questions about building views. 

  • 0

    I need to create a view to list all the tickets with a not null particular custom field. Is this possible?

  • 0

    I have added a Custom Field to my tickets, it is a text box which we use to place the JIRA Bug # if there is one.  I would like to create a view using that field as a condition, but does not let me choose.  How can I get that field as one of my conditons??

  • 0

    To answer JerryK's question: No, it's not currently possible create a view from a custom text field. You can only do that with drop-down lists and checkboxes. This is a current feature request. 

  • 0


    Is it possible to have view that provides resolution time?

  • 0

    I was wondering how to change my views to a particular set without being forced to use the shared views? I am an admin.

    The only solution I can think of is to require my other admins to create their own views and have no shared views, but I want to try to avoid this.

  • 0

    Hey Josiah: 

    If you've got a lot of shared views, you don't want to change that setting, as your other agents would lose access. I'd recommend recreating those views as personal views. Keep in mind that even if your other agents created personal views as well, they could create the view with the exact conditions, and you'd all be looking at the same tickets. 

  • 0

    Hey Justin,

    Thanks for replying. I guess what I'm asking is how do I only use my private views and not the shared views? I like simplicity. I have about 4 or 5 views that I use. Meanwhile there are about 10 views overall that are shared. Is there any way of sort of disabling a shared view only for the current user?


  • 0

    You could use the Agents in Group setting to change availability. This would prevent the views from showing up in that drop down list unless you were in the group. Unfortunately, there's really no way to selectively disable the shared views per user. 

  • 0

    Is there a maximum of views? i add 6 extra's but i can't see them all.

  • 0

    You might need to rearrange your views! You can definitely see more than 6. The first 12 of your shared views and 8 of your personal views appear in the list. If you have more views, the rest of your views can be quickly accessed by clicking the More link at the bottom of the list. You can set the order of the views by reordering the views.

  • 0

    what view I shall create to see tickets transferred by other agents to me? 


    for example, End-User_X created email ticket which has been originally assigned to Agent_A. Agent_A commented on the ticket and transferred to Agent_B, which already had 10+ open tickets. The question is which view to create so that ticket from End-User_X will not get lost among 10+ tickets already assigned to Agent_B. 


    In general - in what view I can sort out tickets which have been either recently updated by either End-Users or Agents? 

  • 0

    You can sort any view by Latest Update in general, or choose latest update by agent/by end user.

  • 0

    Tenley, thank you. The main problem with your suggestion is that agent need to think every time and search for tickets which have been updated by other agents.


    I'm attaching a screenshot which demonstrates the issue - on top you have a section with tickets updated by end-users. this is ok for me since they are visually distinguished from all other tickets. under them you have a list of tickets updated by agent, not specifying either they have been updated by current agent, or transferred internally from other agents with request to action. 

    In Mojo (a product which we are using now) all tickets either updated by end_users or other agents & transferred to current agent go into one same list making life easier to address them fast without any additional search or filtration. 

  • 0

    The updated by filter is probably your best bet here, but it won't show you which specific agent updated the ticket. You can always add tags into your workflow and build views based on the updater and the tag. If agent J updated the ticket, he'd apply a specific tag to the ticket before transferring it. The other agents could then share a view to see which tickets were updated by that agent. 

  • 0

    Justin, I'm bit surprised that we need to code some sort of a script which will add/remove tags in order to keep track of transferred tickets. Do you have examples how your other clients address it?

    otherwise I will have to say that your smaller competitor offer much straight forward approach. 

  • 0

    I didn't say anything about a script! Tagging is built in to Zendesk. You can manually add tags to the ticket when you're working on them, or you can have your triggers add tags for you. First, make sure tags on tickets are enabled from Settings > Tickets. 

    If agent Andrew simply added his name as a tag to the ticket when he was working on it, or transferring it to another agent, all you'd need to do is update your view to look for his tag. Or you could create a separate view to manage tickets that Andrew is associated with. Additionally, you can use the Assignee is condition in the view to filter tickets assigned to those specific agents. 

  • 0

    Justing, I still don't understand how to create a group of tickets which were updated by agents & end_users. After few attempts I've ended up with list of tickets, which need to be sorted out manually by current_agent to figure out which need to be address due to end_user or other_agent request. In Mojo there is just one list on what the current_agent has to focus right now. After two days playing with Zendesk can't created anything similar.

    this is the only reason why we are not migrating to Zendesk so far. 

  • 0

    Hey Peter: 

    I'm going to create a ticket for you with your last comment to discuss further. I'd like to walk you through some setup instructions and try to better understand what you'd like to accomplish. Stand-by for an email! 

  • 0

    "When viewing tickets in a view, positioning your mouse over a ticket title displays essential data about it..." I love this, and use it all the time. However, it would be really helpful if the internal comments were displayed with the same yellow background they have inside the ticket. Right now (at least in Lotus desk) all comments internal and public are displayed with the white background, meaning you have to open the ticket to see if it's public or private. Sometimes it's obvious it's private, more often for us, it's not obvious. 

  • 0

    Is there a way to make a view your favorite?

    So it is possible to start zendesk with your favorite view? e.g. by 'attaching' to the icon bar?

    Now I have to look up and start a view every time again. It would be very helpfull if an agent could start zendesk with his personal favorite

  • 0

    I just have my browser set so one of the pages which loads on start up is the View I use most. I have a couple of other ones as shortcuts in the Bookmarks Toolbar.

  • 0

    So, is there no way to create subsets of Views, similar to Macros (and use of "::")? Is it on the roadmap? Seems like a good request?

  • 0

    Views can't be nested like macros at the moment, Mike. It is currently not on the roadmap to my knowledge, though I've seen a few feature requests pop up. 

  • 0

    I'd like to see this as well. We have so many views, they don't all fit on the drop down. Categorizing them would be nice as well.

Powered by Zendesk