Hi Nagy:

I have struck out on trying to reproduce this in my tracker.  So I am
starting from scratch (simpler tracker) to reproduce the problem.

My plan is to start with the classic tracker. Change the schema for
the status class removing the order property and adding:

   ord = Integer()

so this is the integer property I will use for ordering. Use
setorderprop('ord') for the status class to get that field to be used
for ordering.

The 8 statuses in the classic tracker will have the same value for ord
as they used to have for order. Except item 5 in-progress will have an
ord value of 15.

If I sort a list of issues in a multilink by the status using
sorted(), I should see in-progress(ord=15) between items with ord
values of 1 and 2.

Then I will change the issue.item template to display items in the
superseder multilink using:

        <a tal:repeat="sup context.superseder.sorted('ord')"
        tal:content="python:sup['id'] + '-' + sup['status'] +
               ','*(not repeat['sup'].end)"
        tal:attributes="href string:issue${sup/id}"></a>

Then I will create an issue with 8 superseder issues, one in each
state.  I should see the superseder issues mis-sorted with
in-progress(ord=15) after unread(ord=1) and before deferred(ord=2)
with the mis-sorted item.

Does this sound like it will reproduce the problem you are describing?