The order of the issues in the issue list is not stable from one refresh to another. This is likely because we are using the order in the hash table as the secondary sort and it isn't stable. This should be fixed, perhaps by using the date as a secondary sort mechanism to look better.
The order of the issues in the issue list is not stable from one refresh to another. This is likely because we are using the order in the hash table as the secondary sort and it isn't stable. This should be fixed, perhaps by using the date as a secondary sort mechanism to look better.
Date: 2012-07-04 18:20:00
User: travisb
I've used the issue hash as a presort key because it's easy and fixes the problem.