Incorrect issue status derived due to out of sequence comments

First off all, great work on the D7 upgrade. Thank you to everyone involved.

I've noticed that the issue status of a couple of old issues in the queue I manage have changed from what they were before the D6 to D7 upgrade. The examples are #1854388: Scheduler settings fields empty on content type edit and #270219: Nodes are not being published. which were both 'Closed' before (not sure what flavour of closed, but they were definitely closed as I saved the issue queue page locally before the the upgrade). It seems to be linked to comments which are being shown out of chronological sequence. The status is taken from the comment with the latest date, but comments beneath these in the queue actually have a later status change.

The first attached file show issue #1854388: Scheduler settings fields empty on content type edit summary where it is now showing 'active'. The second image shows the final three comments, in the wrong sequence. Comment #7 has the highest timestamp so the overall issue status is taken from that comment, however #8 and #9 change the status, and it should be closed.

A similar problem appears with #270219: Nodes are not being published. where this is showing 'fixed' but was last updated over five years ago.

Jonathan