Richard Vanderlubbe

We recently upgraded to the enterprise version. It still had a limitation on the number of views on the left nav. Having said that, we were directed to an app in the store that we installed called Quick View or Quickie or something LOL. It's a little magnifying glass in the top right hand corner where you start typing and it short lists matching views. Huge difference in usability. We also did work with groups to limit views that were irrelevant to many support agents and it's all working much better.

Drag And Drop Sort Order By User/Login

Our users are frustrated by the inability to create their own sort order for views.  I've seen a bit on the 12 limitations - agree - when one can scroll, I don't see the need to restrict this, other than perhaps, rendering time if there are many views.

If the user could expose them all, then drag and drop for their favourite 12, and have an expand link (show more) or paging or something to all the views they have, it would help.  Also, a quick filter for all their eligible views.  Right now they have to click manage views, type the partial name - very awkward, especially for managers wanting to keep on top of certain views.

Our users are frustrated by the inability to create their own sort order for views.  I've seen a bit on the 12 limitations - agree - when one can scroll, I don't see the need to restrict this, other than perhaps, rendering time if there are many views.

If the user could expose them all, then drag and drop for their favourite 12, and have an expand link (show more) or paging or something to all the views they have, it would help.  Also, a quick filter for all their eligible views.  Right now they have to click manage views, type the partial name - very awkward, especially for managers wanting to keep on top of certain views.

I was attracted to Zendesk knowing there were credit card encrypted fields.  For the life of me, I cannot figure out how they could possibly be useful.  After input, the card is masked.  I see no value in capturing a masked credit card.

Rather, I expected to have a PCI compliant capture of the card, and expiry date, allowing our agent with appropriate permission the ability to expose this card and log the time stamp and user that viewed the card.  The card should then be redacted.

Or, a secure way to pass this card using the API to a 3rd party application in a PCI compliant way.

If none of these are possible, I do not see any value in the field type unless I am missing something.  It seems we have to build our own forms to capture these cards, and being advised to use a Text field to capture the card in a non-compliant way makes no sense to me.