The help center, by default, offers the option for end users to submit requests. End users who submit requests can also manage their support requests in the customer portal.
The new request list experience (Beta) improves the way in which end users can manage large numbers of requests in the customer portal. When you enable the new request list experience in your theme, end users can use the new combinable filtering options to refine the requests they want to manage as well as new column configuration options to show/hide both system fields and custom fields.
This article contains the following topics:
Enabling the new request list experience
If you have the Copenhagen standard theme, you can use the theme settings to enable new request list experience functionality.
To enable the new request list experience in a standard Copenhagen theme
-
In Guide, click the Customize design icon (
) in the sidebar.
- Click Customize on the theme you want to update.
- In the Settings panel, click Requests list.
- Select the New request list experience check box.
- Click Publish.
If you do not have the Copenhagen standard theme, you can either download a new Copenhagen standard theme and follow the instructions in the previous section, or you can edit the code of your custom theme to include the {{request_list}} helper.
To add the requests lists helper to your custom theme
-
In Guide, click the Customize design icon (
) in the sidebar.
The Themes page opens. - Click Customize on the theme that you want to edit.
-
Click Edit code.
- Under Templates, click requests_page.hbs.
-
Add the following request list helper code to the theme’s main “container” element:
{{request_list}}
For example, when placed in the “container” element in the Copenhagen theme, the request list helper code resembles the following:
<div class=”container”>
{{request_list}}
</div> - Click Save.
Using the new request experience to track your support requests
You can use the help center to track your support requests. If enabled, the new request list experience lets you apply advanced filtering to tickets, helping you quickly locate and manage tickets based on your search criteria.
To track your support requests
-
Click your profile icon on the upper-right side of any help center page, then click Requests.
By default, the page displays all requests that you have submitted with the following columns: Subject, ID, Created date, Updated date, and Status.
To show or hide columns on the page, click the option button () and then either select or deselect the system and custom fields you want to view or hide, or click See more columns to open a separate window where you can show more columns. All columns that are displayed in the list of requests are also shown in the drop down menu together with the six system field columns.
To show custom fields to end users in the new request list, the field permissions must be set to either Customers can edit or Customers can view. See Adding custom fields to your ticket and support request form.
Team members will be able to see fields that have the Agents can edit permission as they would have access to those fields in Agent workspace. This is also the case if you are an Admin assuming an end user account. -
To filter your requests, you can select the Filter drop down, then either select the filter and sub filter you want to apply, or select See all filters to open the Filters window shown below, where you can select and apply filters and sub filters.
You can select multiple filters to further refine your search criteria. You can also filter on values in fields where you have hidden the column.
When you select more than one filter, the filters act as an "AND" search criteria, meaning that requests must meet all filter criteria in order to display. When you select multiple filter options within a single filter, they act as an "OR" search criteria, meaning that tickets must meet one or more criteria in order to display. For example, if you select both "Awaiting reply" and "Open" within the Status filter, tickets can have either an "Awaiting reply" or an "Open" status to display.
Filters that you apply appear beneath the search field and can be cleared at any time by clicking Clear filters.
-
To search your requests, enter a search term in the Search Requests box.
You can use ticket property keywords in your search. -
To see details about a request, click the request title.
If you belong to multiple organizations, you can change the organization for a support request when you view details for that request.
Tracking your organization's support requests
As an end-user you can be a member of one organization or multiple organizations. If you're a member of a shared organization, you can see tickets for all members of that organization.
To track your organization's support requests
-
Click your profile icon on the upper-right side of any page, and then click Requests.
-
Click the Organization requests link on the My requests page to see all the requests in your organizations. The link appears only if you're a member of a shared organization.
To show or hide columns on the page, click the option button () and then select or deselect the system and custom fields you want to view or hide.
-
To filter the requests, click Organization to select the organization that you want to view tickets for, then click the Filter drop down to select the filter and sub filter you want to apply. You can select multiple filters to further refine your search criteria.
When you select more than one filter, the filters act as an "AND" search criteria, meaning that requests must meet all filter criteria in order to display. When you select multiple filter options within a single filter, they act as an "OR" search criteria, meaning that tickets must meet one or more criteria in order to display. For example, if you select both "Awaiting reply" and "Open" within the Status filter, tickets can have either an "Awaiting reply" or an "Open" status to display.
-
To see details about a request, click the request subject.
You can add comments to a request if an administrator has set it up. For more information, see Setting up a shared organization for end-users.
To subscribe to requests for a shared organization
- Click your profile icon on the upper-right side of any page, and then click Requests.
-
Click the Organization requests link on the My requests page to see all the requests in your organizations.
The link appears only if you're a member of a shared organization in Zendesk. -
Click Follow organization.
If the Follow organization button is not available, ask your administrator to add it to your help center theme (see Add Follow/Unfollow for users in a shared organization).
You will now receive notifications for new and updated requests in your shared organization. - Select the organization that you want to follow, then click Save. You will receive updates about tickets in each of your selected organizations.
If you do not have the Copenhagen standard theme, you can either download a new Copenhagen standard theme and follow the instructions in the previous section, or you can edit the code of your custom theme to include the {{request_list}} helper.
Filter options and behavior by field type
Zendesk provides custom field types for tickets, users, and organizations. Although the fields displayed in the request form and request list are custom field types, they often have unique names that reflect their purpose. For example, the request list may display a field named “Store location” that is a drop-down field type designed to let users select from a list of store locations. In this case, the request list will display the field name “Store location,” even though it is a drop-down custom field type.
For a list of custom field types that you can filter on, see About custom field types.
66 Comments
@... I am not sure I understand correctly? Are you saying that whether we use Customer Profile Page some how affects whether we have Requester available as visible column on the Organizational tickets list for our customers using Guide / My requests page?
Your earlier instructions did not apply to Organizational tickets view, the Requester column is not available for selection.
Are there plans to allow filtering on additional fields added to the list view? Like Type (OOTB) or Product (Custom).
Gorka Cardona-Lauridsen
Is it possible to use this new beta {{request_list}} and customize the request list view with custom headers?
I am finding that enabling beta disregards any of the custom fields I changed due to the {{if settings.request_list_beta}} boolean.
I really like the new filter and organization view but still want the ability to customize views.
Hi Siddharth.Jain
I assume you have implemented {{request_list}} helper in your custom theme.
I have not been able to reproduce that agent-only fields would show up in the new request list experience.
What I have been able to see is that if you visit the request page with and Admin or Agent user then that Admin or Agent user can see agent only fields (intended behavior, but documentation needs to be updated). If you then within the same browser session logs out with your admin or agent user and logs in with an end user, then that end user sees the Agent only fields because they are cached. I have created a bug report to fix this issue.
Could that be the reason in your case?
Hi Zendesk team!
Can you share some plans for this beta requests list? And namely, if it's planned to add export functionality for customers, so that they could get all tickets in one file?
Another thing, is it possible to add requester name or email to the list of requests in “Requests I am in CC” tab and “Requests of my organization” tab? It could be really useful for “large” customers.
Travel Syndication Technology if it still does not appear I would advise you to create a support ticket so we can help you troubleshoot.
I'm also that seeing that inactive customer fields are showing up as options for columns - can the inactive fields be removed as an option?
Hey Gorka Cardona-Lauridsen!
Does request list introduce a possibility to view requests for an end-user across all brands?
Original tread about this feature request:
https://support.zendesk.com/hc/en-us/community/posts/4624230371866-Enable-end-users-to-view-all-their-multibrand-requests-on-a-single-Help-Center
I have also noticed that there are some rows in the view where the Subject field is empty.
The subject name will reveal only when hovering the line:
This is before hovering:
This is after hovering the field:
This doesn't happen to all of the rows, only for a few.
Gorka Cardona-Lauridsen thanks for getting this fixed so fast. We rolled it out to customers last month and they really seem to like it
Siddharth.Jain were you doing this through the browser (new login session) or were you previewing as a user. The only reason why I ask it that when support was trying to reproduce my original issue there were previewing as a user from Guide and the user had admin permissions. I just tested this on my site and it isn't happening
Gorka Cardona-Lauridsen I am trying to use the new custom status on this page and they do not show up in the filter - are these available yet? I know they show up when you click the actual ticket just not in the page view. The strange part is it will flash on the right side of screen for a second and then disappear - similar to the issue I had above. Below is an example of one I created on a custom field and the second screen shot is one we have of a standard field that was renamed
Gorka Cardona-Lauridsen
We see the same issue like John DiGregorio:
For customers, who never played around with additional columns / tickets fields in the request list the status column is missing and the field is also not available to be added manually.
In my profile I already added some more fields / columns and the status field is not missing.
Can you reproduce this behavior?
If so, is there a rough idea by when the problem will be fixed so we can communicate this to our customers?
If no: If you need access to our instance for debugging you are very welcome to contact us.
Oh, will cross post my question here too, so what I'm trying to do is to tweak Copenhagen theme and have home page to reflect only list of the requests. But getting errors when copying container from requests_page.hbs to home_page.hbs:
Any hints how one can make that container to work on home page?
Thanks!
Jason Kim The request list view is not code customisable since we want to be able to iterate fast on this component and not risk breaking customised themes at the moment. This is one of the reasons it is currently in Beta, but we are aware of the need to customize this functionality and are considering different options to make that possible.
The entire component is built with REACT and uses our Requests REST API, there's no serverside "magic", so if we where to make the code open source so you could get it from Github and put it into your theme and make any modification you want - would that work for you?
Travel Syndication Technology I had the same problem with it not being on the menu and I was on version 2.0. I was able to modify the code. However, after I made some changes I got the same error as you. I logged out and back in and the error went away.
Gorka Cardona-Lauridsen one I had the code in I had an issue where it was displaying the old list under the new list. I had to spin up a fresh sandbox, copy clean code, and then apply it, and now everything works great
Viktor Osetrov the issue is in the Organizational requests view for customers - the Requester is missing as an option to filter or add to the columns. My customers need to be able to see who is the requester and be able to filter on this. It was in the original requester screen, how can we add this back to the beta version.
Josef Prandstetter and John DiGregorio
Apologies for the late update on the bug. We rolled out a fix for the missing Status column bug last Thursday.
Hi Gorka Cardona-Lauridsen, thanks for the update. I also want to point out that even on the out of the box requests page the new value appears in the view results but not in the filter.
Shawna James This feature is really cool, however; it will be confusing for our end users when they have to scroll through custom fields that belong to several different forms. Is there a way to group the fields by form so it's easily understandable what fields belong to which form? This is something preventing me from recommending it to our team.
Tagging Gorka Cardona-Lauridsen
Gorka Cardona-Lauridsen
Yes - that can work for now. Do you have any timelines of when this will come out of beta?
Gorka Cardona-Lauridsen thanks for the quick response. I apologize for pushing the issue. However, these are features our customer base would like to see. I even reached out to a 3rd party consulting company to see if we could pay to get the export to CSV and Excel
Hi all
We are very excited to announce that users can now (pending rollout) filter their requests based on custom field values in the new request list experience. See the announcement here for all the details.
We have a customer who would like a copy button for all the contents of a code block so they easily transfer it into an external editor.
Why would the filter show ALL of our internal/agent only fields to customers? seems silly
For troubleshooting, please go to your Manage Views.
For your specific view click on "three dots" settings and then press "edit view" and add a "Requester" Column to the "Formatting options" area
Please notice that you can choose up to 10 columns to appear in your view. Drag and drop to reorder them.
Hope it helps
Travel Syndication Technology you are most likely seeing this error because you are using your theme is using templating API v1 and not the latest that is v2. I realise I had forgotten to have that called out in the documentation, apologies for the inconvenience. We will add that pre-requisite.
To learn more about the different versions of the templating API and how to upgrade see:
Brittany Mandel
I have the same problem with my brand text color, but my customers have really taken to the new requests list, so to work around it, I replaced $brand_text_color with #fff in my css. Not the most elegant solution, but it works.
I have been struggling for days with support as they are not emulating the user correctly and when they do their testing they have full admin rights - it is very frustrating, and I am getting ready to turn the feature off.
We have an end customer who request that the number of tickets displayed on the Requests page be configurable from the default of 15.
Please sign in to leave a comment.