Thraxisp suggested to paste the contents of one of the filters, on the supposition that this might be the behavior of a corrupt filter. It appears clear, but for the sake of being complete:

v7#a:33:{s:8:"_version";s:2:"v7";s:10:"_view_type";s:6:"simple";s:13:"show_category";a:1:{i:0;s:1:"0";}s:13:"show_severity";a:1:{i:0;i:0;}s:11:"show_status";a:1:{i:0;i:0;}s:8:"per_page";i:500;s:17:"highlight_changed";i:6;s:11:"reporter_id";a:1:{i:0;i:0;}s:10:"handler_id";a:1:{i:0;i:0;}s:4:"sort";s:2:"id";s:3:"dir";s:4:"DESC";s:11:"start_month";i:8;s:9:"start_day";i:1;s:10:"start_year";i:2006;s:9:"end_month";i:8;s:7:"end_day";i:7;s:8:"end_year";i:2006;s:6:"search";s:0:"";s:11:"hide_status";a:1:{i:0;i:-2;}s:16:"and_not_assigned";b:0;s:15:"show_resolution";a:1:{i:0;i:0;}s:10:"show_build";a:1:{i:0;s:1:"0";}s:12:"show_version";a:1:{i:0;s:1:"0";}s:17:"do_filter_by_date";b:0;s:16:"fixed_in_version";a:1:{i:0;s:1:"0";}s:13:"show_priority";a:1:{i:0;i:0;}s:12:"user_monitor";a:1:{i:0;i:0;}s:10:"view_state";i:0;s:13:"custom_fields";a:0:{}s:13:"sticky_issues";s:3:"off";s:17:"relationship_type";i:-1;s:16:"relationship_bug";i:0;s:12:"show_profile";a:1:{i:0;i:0;}}

1 > Had this issue suddenly on one fine morning on 0.19.4 - Upgraded from 0.19.4 to 1.0.5 - still problem persist

2 > Tried on my personal computer, the same database backup with 1.0.5 - No probs faced.

I think it has something to do with some files or so? Can somebody tell us?

This is a duplicate of 0007324.

As it says right in the bug text, this is not the same bug as 7324.

• The sort is not gone, it is incorrect.
• The bug that has been reported to MySQL in 0007324 does not cause this flaw.
• Creating a new bug tracker on the same box and moving the data to the new
  tracker, the new tracker works correctly. Another user has also reported
  this.
• My box does not run 4.1.21, which causes the MySQL bug, but rather 4.1.20,
  which is known to not cause 0007324.
• The machine was not upgraded at the time the box broke; this database used
  to work for Mantis just fine, but suddenly fails.

This is not 0007324. False duplicate; re-opened.

Thank you for taking the time to report a problem with mantis.

Since this problem report was originally made, a number of releases have occured. Additionally no recent feedback has been received on this issue.
It appears that this issue has either been fixed, or may not be a relevant report for the current release.

Unfortunately you are not using the latest version and the problem might already be fixed. Please download the latest release from http://www.mantisbt.org/download.php

If you are able to reproduce this bug in the current release, or have some more information on how this feature could be improved in the current release. Please either change the mantis version on this bug report
to the version you tested and change the status back to "Open", or open a new issue report with more information.

Again, thank you for your continued support and report.

Still happens in current Mantis. Easily reproduced. Two years later, you guys haven't fixed this, and you're still looking for a way to bury it.

Not fixed, still reproducable

Hello StoneCypher,

Can you make this happen on www.mantisbt.org/bugs ?

I'm quite willing to fix it but when I tried to reproduce this issue on my test database, I wasn't able to.

Paul

Resolving since it has been a year without a response.

Still very easy to reproduce. That's the third time vboctor has incorrectly closed this defect.

It's been more than three years.

As there is no feedback for 0007369:0020163 I am closing this issue as not reproducible.
Feel free to reopen the issue and provide a reproducible workflow if there are still problems after updating your installation to latest version.
If the problem still occurs with latest stable version (1.2.2 atm) you could help by trying to reproduce the issue with 1.3dev version. There are also filter related sources changed in it.

What I find most fascinating is that today, four years to the day after I reported this, none of you have even tried to reproduce this. I haven't even touched mantis since 2007, mostly because you guys won't put in any effort to locate the defect that tore my bug database apart and made it unusable.

First, your owner made a ridiculous duplicate mark. Removed..

Then, two years and three months later, someone said "We changed a lot of stuff, so I'm burying this without identifying it." Removed.

Nine months later, the same moron who pretended a serious defect was an obviously wrong dup said "it's been a year since response" (it had actually been nine months,) so I'm burying it again." Fixed.

So I reproed it on an up to date bug tracker. Three years later, and I can repro it in under five minutes, using only the things I said in this bug, even though I moved on to Flyspray back when George Bush still had years to go in office. (Why? Because Flyspray developers don't stick their fingers in their ears and pretend serious data loss bugs aren't real.)

Rattle forward a year and a month, and here you are doing it again.

I just downloaded Mantis. It still reproduces. You're just too lazy to track it down, so three of you have now five times tried to inappropriately bury the data loss bug.

And you wonder why, ten years into development, you're still in version one, chasing serious bugs in a bug tracker, with very very few long term users.

If you had just waited twenty two hours, I could say "more than four years."

C'est la vie.

Still reproduces. Stop telling yourselves stories. This bug is active, open, and being ignored for FOUR YEARS.

You guys are awesome.

For nearly four years you've had a data loss bug marked as a duplicate of "sorting gets broken after mysql upgrade."

And now you're taking away people's ability to report bugs by closing tickets in a way that they can't be re-opened.

Seriously, quality work, guys. I reproed in under five minutes.

Thank god I moved on more than three years ago.

Still think this should be fixed by someone who knows the difference between "I lost data" and "it won't sort anymore."

Start by unassigning this from vboctor, who botched this more than four years ago, and hasn't looked back since.

Someone should take a look at 7324, to understand how stupid the duplicate mark actually is. The fact that you've had this marked as a MySQL version-specific bug despite that it wasn't even that version of MySQL isn't even the stupidest part of that mis-file.

I am no native English speaker, so maybe I don't understand how to reproduce the problem.
Believe me that I tried to reproduce what I understood without seeing a problem.
If you are interested in getting this fixed, please provide a simple step by step instruction what I have to do and how I can see the problem.

StoneCypher,

You did not provide any feedback; I am therefore resolving this issue again as "unable to reproduce".

Feel free to reopen the issue at a later time and provide the requested information.