Dan Hillesheim

@Jason - Unfortunately, according to ZD, this isn't on the "public" radar and it's not a big enough issue to be addressed at this time. You're right, it is ridiculous that we can't customize this within Zendesk. It should be a standard feature to adjust the view to be what your customers need it to be without investing more time and money in having someone develop a custom solution. We are stuck using it because we already have so much invested in it. I would love to see some action on ZD's part to move on this particular issue.

@Chuck Yocum

If you figured out a way to export to excel that would be a great thing. If you're willing to post, please do!

@Mark Harper 

I looked at your code and I can't see anything egregious. I know it may sound stupid, but did you enter in your actual subdomain instead of "mydomain"? I've made that same mistake many times. Also, I would check to make sure that the Reguest API is the one you need. I know that in my script I had to change the api call to "api/v2/tickets/" instead of "api/v2/requests/"  and change 'data.request.fields' to 'data.ticket.fields' because "request" didn't have access to the custom "ticket" fields we wanted to show. 

I'm going to keep looking for a better way to do this. I don't like how cumbersome it is. And, yes, Zendesk should have this type of functionality baked in. This is a pretty common request it seems and I bet there are even others who need it, but just deal with it because of time. 

I'm new to Zendesk, just started on this project. I was looking for a way to show custom fields (four in total) in the Request List page and be able to sort by them as well. I got this solution working, but might there be a more elegant way to pursue this? I'm thinking between the placeholders and liquid code we should be able to stash the where they belong and just query the api and loop through the response for each ticket. Has anyone had success using a different method?

My thought is to break up the inline JS as to not be looped by the template and create so many unnecessary calls. If we make the API call and get back the JSON, create a global object, then we can put a smaller request in the foreach loop so we're requesting existing data and not making so many api requests per ticket. Does that make sense?