You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it's very non-intuitive behavior when the photo which is highlighted is the one which will be kept. the problem is that we click "trash" button, so every time when i delete duplicate i have to ignore this button to not be confused.
It would be more intuitive when the photo with "trash" tag would be highlighted to red, because we will click button "trash", so yea. the same when we add photos to album. we select photo we going to add to album. Not the photo we not going to add.
The OS that Immich Server is running on
TrueNAS
Version of Immich Server
v1.106.3
Version of Immich Mobile App
v1.106.4
Platform with the issue
Server
Web
Mobile
Your docker-compose.yml content
not matter
Your .env content
not matter
Reproduction steps
1. go to "Utilities"
2. then"review duplicates"
3. if more than 1 duplicate photos you will see highlighted photo to keep
4. click "trash" button which will delete every thing which is not highlighted (and with tag "trash")
Relevant log output
No response
Additional information
The text was updated successfully, but these errors were encountered:
The bug
it's very non-intuitive behavior when the photo which is highlighted is the one which will be kept. the problem is that we click "trash" button, so every time when i delete duplicate i have to ignore this button to not be confused.
It would be more intuitive when the photo with "trash" tag would be highlighted to red, because we will click button "trash", so yea. the same when we add photos to album. we select photo we going to add to album. Not the photo we not going to add.
The OS that Immich Server is running on
TrueNAS
Version of Immich Server
v1.106.3
Version of Immich Mobile App
v1.106.4
Platform with the issue
Your docker-compose.yml content
not matter
Your .env content
Reproduction steps
Relevant log output
No response
Additional information
The text was updated successfully, but these errors were encountered: