We’ve identified this to be if a ticket disappears, possibly from corruption as no manual deletions were used.
You can find your missing tickets pretty quick by doing the 50% range:
Enter a random low number ticket until you find one that URL and ticket match:
/10001 for example
then find a ticket that doesn’t match,
/19001 for example.
14501 match yes, then try 17501, or no match try 12501.
Then keep doing half match or no until you find the missing ticket.
Yes I think this is an issue, as often ticket numbers are shared in other platforms and the URL should reflect the ticket number since that’s how it was expected to function. If the URL was completely abstracted from the ticket number that would be different, however I think it’s expected they should match, as they only don’t match when this happens.
BTW our first missing ticket was number 27812. So almost 30k tickets before an issue, but from there on out they’re off.
We have identified our missing ticket as: 231066
Is there way to insert a number somehow to correct this issue?
@MrGeneration it is not a technical issue, but it is annoying because when reffering/sharing a link to another (messaging)application we often would copy the url. When then reading this on your smartphone and want to quickly enter it in the PC’s webbrowser within Zammad we search for the ticketnumber part. When it matches, you get to the correct ticket. Now you don’t. Than you have to wonder, was it +1 or -1 from what I see in the URL?? So, annoying…