Ticket System does not reset to <ANY Ticket System> after batch update. (4260291)

Ticket System does not reset to <ANY Ticket System> after batch update.
After running batch update to remove the ticket system requirements, the default ticket system remains selected.
This causes users to be unable to request for password/session when TPAM requires the user to enter a ticket number for a non-existant system.

This issue affectes both 2.4.804 and 2.5.910. Issue resolved in hotfix_6336 and 2.5.912
The latest version of TPAM can be download from the portal.

After the fix, the similar issue may still be reported, but this is likely a different problem caused there are lots of system to be updated and the database query timed out.  If the implementation is only for 1 Ticket System, it may be better to plan the batch update to <ANY Ticket System> before making any changes.