Sorting does not work after upgrading to 10.11.0

[patrickdk77]

Description of the bug

Upgraded to 10.11.0 and now when soring a library by date added, date epsiode added, date played, date released, the order seems random, it's not even close to being correct as it was previous to the upgrade. This is happening in all my libraries. series that a years old are shown to be the newest

This is not affecting recently added though.

Reproduction steps

install 10.0.0, add series, note order, upgrade to 10.11, note order

What is the current bug behavior?

not in date order

What is the expected correct behavior?

should be in the date order selected for the library

Jellyfin Server version

10.10.0+

Specify commit id

No response

Specify unstable release number

No response

Specify version number

10.11.0

Specify the build version

10.11.0

Environment

- OS:ubuntu 24.04
- Linux Kernel: 6.8
- Virtualization: docker
- Clients: browser
- Browser: brave
- FFmpeg Version: none
- Playback Method: none
- Hardware Acceleration: none
- GPU Model: none
- Plugins: none
- Reverse Proxy: none
- Base URL:
- Networking:
- Jellyfin Data Storage:
- Media Storage:
- External Integrations:

Jellyfin logs

[2025-10-26 12:53:12.503 -04:00] [INF] [72] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "127.0.0.1" request
[2025-10-26 12:53:14.210 -04:00] [INF] [72] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "127.0.0.1" closed
[2025-10-26 12:53:14.692 -04:00] [INF] [71] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "127.0.0.1" request
[2025-10-26 13:03:02.693 -04:00] [INF] [39] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.

FFmpeg logs

Client / Browser logs

No response

Relevant screenshots or videos

No response

Additional information

No response

[Shadowghost]

Should already be fixed by #15187 - please close if 10.11.1 fixes this once released

[patrickdk77]

Hmm, there is no 10.11.1 release, if there was I would have tested it.

[Shadowghost]

As I wrote: "once released", fix was already merged but not released with any version.
Should be available now.

[patrickdk77]

It somewhat works with 10.11.1

Show by date episode added works correctly.
But Date Show Added still does not work, it's showing shows where all added recently that are years old.
It says it uses the value from libraries->display->date added behavior, that is set to Use file creation date

in jellyfin it says, Date added: 09/25/2025 in the shows metadata

But I have:
Access: 2023-04-13 21:17:43.687668779 -0400
Modify: 2025-09-25 12:16:25.791401535 -0400
Change: 2025-09-25 12:24:01.344135077 -0400
Birth: 2021-11-06 01:31:40.711826239 -0400

So it's not using creation date, but modified or change date instead now.

[Shadowghost]

What happens if you do a replace all metadata on such a show? We fixed some things in the date handling, so it's quite possible that you had bad data in the DB before and it just only showed now.

[patrickdk77]

That did not work out :(

This happens for any show I do replace all metadata on, the date goes to 01/01/1901

[welshtralian]

Hello. As the title is quite generalised, I would like to add that the sort order (by channel number) on Live TV isn't correct either, it seems to be based on recent channel watched. I've clicked on the radio buttons to recently watched and then back to by channel number to see if that resets the order but it does not.

[patrickdk77]

This is really painful. All the date added fields have been reset, on every tv show, music, book, live tv entries.
It seems new items added after 10.11.1 work ok, but anything that was added before 10.11.1 is messed up.

10.11.2 does not fix anything either, they are all still messed up after a rescan.

[urbenlegend]

It seems new items added after 10.11.1 work ok, but anything that was added before 10.11.1 is messed up.

Does that mean deleting the library and recreating it will workaround the issue for now?

[patrickdk77]

No, as if you delete it and recreate it, all the dateadded will be the current date. That is not much different from every date being 1901, so same problem, just different value.

[patrickdk77]

It does mean, going forward, if the problem is fixed, it will not be wiped out anymore by doing a rescan though.