Album release always reverts after import

[haath]

Is there an existing issue for this?

• I have searched the existing open and closed issues

Current Behavior

It seems that Lidarr does not honor the manual choice of album release, and automatically reverts to another one when I import files. For example, after selecting a 12-track release and importing 12 files, Lidarr automatically switches to another release with 13 tracks and shows the album as 12/13 incomplete.

I have also confirmed that the first 12 tracks are the same on both releases, so it's probably not a name conflict or anything like that.

The behavior is the same whether I try to manually import a downloaded item from the Queue, or I press Manual Import from the artist page. And I have had this for multiple albums over multiple artists, it's not an incident specific to one album.

Expected Behavior

I expect Lidarr to honor my manual choice of album release, and not revert it when I import the files.

If I select a release with 12 tracks, and then I import 12 matching files, I expect the album to turn green showing 12/12 and that should be that.

Steps To Reproduce

1. Go to album and press Edit
2. Untick Automatically Switch Release
3. Select a release from the list with 12 tracks
4. Import 12 files
5. Lidarr now automatically switched the release to another one that expects 13 tracks, as a result the album is now red showing 12/13
6. Open Edit menu again, re-select the 12-track release
7. Lidarr now loses all files, the album is now red showing 0/12. The Refresh & Scan button does not resolve this at this point.
8. Attempt step 4 again, and it's a repeat of the same

In case it is relevant, here are my media naming formats:

• Colon Replacement: Smart replace
• Standard Track format: {Release Year} - {Album Title}/{Artist Name} - {Album Title} - {track:00} - {Track Title}
• Multi Disc Track Format: {Release Year} - {Album Title}/{Artist Name} - {Album Title} - {Medium Format} {medium:00} - {track:00} - {Track Title}
• Artist Folder Format: {Artist Name}

Environment

- OS: Ubuntu 22
- Lidarr: 1.3.5.3530-ls134 by linuxserver.io
- Docker Install: Yes
- Using Reverse Proxy: Yes
- Browser: Firefox
- Database: Sqlite 3.41.2

What branch are you running?

Master

Trace Logs?

The full logs

lidarr.txt

In my example I am referring to the Violent Revolution album of the band Kreator, but I have had this bug occur on many albums.

Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided.

• I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue.

[haath]

Nevermind I just now realized that you are supposed to select an album release every time when manually importing, and it defaulted to a different one than the one I had selected.