Redmine

1. click on project,
2. click on issues,
3. get. eg. open issues,
4. review them using "prev"/"next" buttons, until found issue which should be closed (but isn't).
5. click update, set it as resolved/closed

RESULT: prev/next buttons disappears, because current issue gets out of query,

SHOULDBE: prev/next buttons should be visible and should point to issues from last running query.

Similar scenario: review list of unassigned tasks one by one and assign appropriately. Impossible using current next/prev implementation.

It works like that in Mantis, I believe that list of issue ids is stored somewhere in session, and prev/next gets data from that list.