Bug found in request selections spanning refresh

A technician reported some issues with tickets he had closed (spam coming in, unfiltered automated monitoring messages).

So I set my selection filter to Closed Requests, was reviewing was he was complaining about and had several tickets selected for a mass deletion.

My screen refreshed (it's set to 1 minute intervals) and while the check marks were still there, they were offset by 1, covering legitimate tickets now.

Yikes! I almost deleted references to real tickets that were closed.

I just checked this with pending requests, and had two checked on the screen, and I created a new ticket. I watched the screen refresh, and sure enough, the checkmarks jumped from the wrong selected tickets to other tickets.

So, to explain it better:

I select the 4th, 5th and 8th ticket from the top in a list of 20 tickets opened.
A new ticket is created, and now we have 21 tickets opened. However, the new ticket shows up at the top, and again the 4th, 5th and 8th tickets are selected. It should have been the 5th, 6th and 9th tickets to be selected...

Hopefully that explains how to replicate it.

Justin