Using the new request list experience in the help center customer portal (Beta)

Return to top

66 Comments

  • Arno (EMEA Partner)

    @... 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.

    0
  • Jim Uomini

    Are there plans to allow filtering on additional fields added to the list view? Like Type (OOTB) or Product (Custom).

    0
  • Jason Kim

    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.

    0
  • Gorka Cardona-Lauridsen
    Zendesk Product Manager

    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?

    0
  • Kirill Akimov

    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.

    0
  • Gorka Cardona-Lauridsen
    Zendesk Product Manager

    Travel Syndication Technology if it still does not appear I would advise you to create a support ticket so we can help you troubleshoot.

    0
  • Lydia Forsyth

    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?

    0
  • Andrey Vasin

    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

    0
  • Ayelet Haiventriger

    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.

     

    0
  • John DiGregorio

    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 

    0
  • Shawna James
    Community Product Feedback Specialist
    Thank you all for continuing to provide your feedback for this feature! We appreciate you taking the time so that our PM's can stay on top of your requests and ideas. 
    0
  • John DiGregorio

    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

     

    0
  • Josef Prandstetter

    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.

    0
  • Andrii Melnychuk

    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:

    11 errors
    'request_list' does not exist
    'filters' does not exist
    'form' does not exist
    'query' does not exist
    not possible to access `requests` in `requests.length`
    'query' does not exist
    'requests' does not exist
    'requests' does not exist
    not possible to access `current_filter` in `current_filter.identifier`
    not possible to access `current_filter` in `current_filter.identifier`
    'requests' does not exist

    Any hints how one can make that container to work on home page?

    Thanks!

    0
  • Gorka Cardona-Lauridsen
    Zendesk Product Manager

    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?

    0
  • John DiGregorio

    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

     

    0
  • Susan Schneider

    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.

    0
  • Gorka Cardona-Lauridsen
    Zendesk Product Manager

    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.

    0
  • John DiGregorio

    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.

    0
  • Lydia Forsyth

    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 

    0
  • Jason Kim

    Gorka Cardona-Lauridsen

    Yes - that can work for now. Do you have any timelines of when this will come out of beta?

    0
  • John DiGregorio

    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

    0
  • Gorka Cardona-Lauridsen
    Zendesk Product Manager

    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.

    0
  • Graham Pearce

    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.

    0
  • Bobby Koch

    Why would the filter show ALL of our internal/agent only fields to customers? seems silly

    0
  • Viktor Osetrov
    Zendesk Customer Care
    Hello Arno,

    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
    0
  • Gorka Cardona-Lauridsen
    Zendesk Product Manager

    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:

    0
  • Amy Gracer
    Community Moderator

    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. 

    0
  • John DiGregorio

    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.

    0
  • Graham Pearce

    We have an end customer who request that the number of tickets displayed on the Requests page be configurable from the default of 15.

    0

Please sign in to leave a comment.

Powered by Zendesk