Hello,

Isn't the purpose of having the ticket ID be randomized to not show the total number of tickets to clients? In addition to the random ID, there's an incremental ID visible to staff-- and more concerningly, visible to clients, meaning it's obvious how many tickets have been submitted in total. This seems like a bad idea, and moreover, there's another perfectly good ID that could have been used instead.

Is there a way to hide the total number of tickets in the URL and use the 6-digit ID instead?

    Naleksuh

    No, that’s not the intention. Ticket Numbers are random by default just because. You can make them sequential if you want we just use random by default. It’s never much of concern at all and IDs are used and visible in endless platforms and softwares. As long as you have the appropriate security measures in place it’s virtually useless information.

    With this being said the code is open source and you are more than welcome to modify it to your liking. However, as with all customizations, you are on your own.

    Cheers.

      "Security" wasn't the point. I wasn't suggesting that number could help attackers. It is bad for business for anyone to be able to determine the number of tickets you have, which is a reason why everyone says not to use incremental counting.

      Also, why are there even two different numbers at all? Isn't it simpler to just have one?

        Naleksuh

        Because the concept of a number and an ID are completely separate. The number is an arbitrary number that can be random or sequential. You can change the number format to your liking and some people like doing things like "22-XXXX" where "22" is the year, etc. The ID is the unique identifier for the Ticket object that we use to reference in other related objects, etc. You can research OOP to get an understanding of IDs and why they are important, etc.

        Cheers.

          Write a Reply...