Sorting the issue list by creation date does not always produce a consistent order when multiple records have similar timestamps. Users may see the ordering change between requests even though no issues have been modified. The database query should use a deterministic secondary sort key, such as the issue identifier, so that records with identical or very close timestamps always appear in a stable order.