Issues in paginated views may be lost because sorting criteria are not unique
This is a problem that the issue that should be present is not displayed on the issues/index.
The same problem may exist even at index other than issues/index.
This problem occurs when using PostgreSQL.
If you use only non-unique fields such as trackers or categories as the sorting criteria, there is a possibility that some issues will not be displayed on pagination views.
This phenomenon is described in the document of PostgreSQL. (As a specification rather than a bug)
Questions about the same problem:
I attached file is the test I wrote to reproduce this problem.
If you are using PostgreSQL, that test will fail. ( Non-paginated issue ids and paginated issue ids should be the same. )
Failure: --- expected +++ actual @@ -1 +1 @@ -[2, 12, 11, 8, 7, 5, 3, 1, 13] # Non-paginated issue ids +[11, 12, 12, 7, 7, 5, 3, 1, 13] # Paginated issue ids