Ticket number collision

[nunolbb]

CUSTOMER ARE GENERATING THE SAME CALL NUMBER.

EXAMPLE: CLIENT NUMBER 1 - OPENED CALL # 195019, WHICH IS ALREADY CLOSED.
THE SYSTEM IS GENERATING THE SAME CALL NUMBER, FOR CUSTOMER NUMBER 2 # 195019. WHEN I CLICK ON THE CUSTOMER CALL 2 HE ISSUES ME FOR THE CUSTOMER 1.

[nickbe]

Can you please post your questions in english so that everyone can participate?

[nunolbb]

OK

[nunolbb]

CUSTOMER ARE GENERATING THE SAME CALL NUMBER.

EXAMPLE: CLIENT NUMBER 1 - OPENED CALL # 195019, WHICH IS ALREADY CLOSED.
THE SYSTEM IS GENERATING THE SAME CALL NUMBER, FOR CUSTOMER NUMBER 2 # 195019. WHEN I CLICK ON THE CUSTOMER CALL 2 HE ISSUES ME FOR THE CUSTOMER 1.

[nunolbb]

I verified that the client can not close the ticket, because this ticket is from another client.

I as administrator also can not close this repeated ticket from another client.

[ivandiazwm]

Ok, I've found the reason for this.
https://github.com/opensupports/opensupports/blob/master/server/models/Ticket.php#L99
We're calculating the next ticket number by counting when we should use the last ticket id instead.
The problem is that if you delete a ticket and it's not the last created, the next ticket number created will collide with the last ticket. This can happen in two two ways: by individual ticket deletion (not relased yet) or by deleting an user with tickets.
@nunolbb Thanks for the reporting this, I'll release a hotfix for the current version.

[nunolbb]

blz!!!

[nunolbb]

How do I put those codes? I understand only the basics of programming.
This system is helping me a lot here in the company. Very cool!

[ivandiazwm]

@nunolbb Please download and decompress this file in your OpenSupports' installation.
This will solve the issue for future ticket creation, for the current collision, change one of the colliding ticket_numbers to 1 directly in the database.