Regarding this article - https://support.zendesk.com/hc/en-us/articles/4628113350170-Using-the-new-request-list-experience-in-the-help-center-customer-portal-Beta?page=3#comment_6645901030810
We turned this on, however, one thing noticed is that users that have "can view tickets from user's org" on their user profile no longer have the system field "Requester" as a column when in the Organization tickets tab, and it's not an available column to add in.
In this article it states:
"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."
How do we get this available for those users as a column to add? This is critical for users who monitor ticket submissions across their org so they can quickly scroll through and see who submitted each ticket, and they are understandably voicing their frustration. The reason we turned this feature on is so that clients who belong to orgs with multiple products, but only deals with 1 of them, can use this new filter option to narrow what tickets they're reviewing across their org.
Also, two additional questions:
1. Is it possible for a user to save what filters/columns they have set? I noticed filters set do not stick when leaving the page and returning.
2. Is it possible for clients to be able to add a "last updated by" column?
These suggestions are really useful, and I am sure many other users will benefit from having them. As of now, these 3 suggestions are not feasible, but, luckily, since this is a beta, our team is looking for this type of suggestions to improve the product.
Because of this, I encourage you yo post your question in the feature announcement post. I see that you already commented in one of the beat posts, and that will help.
Our PMs are actively taking feedback from these posts to improve the feature before its final version.
Thank you!