If I filter my collection on (for example) lastplay:26/04/2014 I'd expect to only see tracks I played on that date but I'm seeing lots of tracks I played on 25/05/2014. I think what's happening is that it takes 24 hours from the current time, so if I filter at 10am I get all the tracks I lastplayed between 10:01 on 25/05 to 10:00 on 26/04? Maybe this behaviour is as intended and the mapping of the exact date to a time interval gives unexpected edge cases? I was out nearly all day on 26th so I wouldn't expect much listening but both lastplay:26/04/2014 and lastplay:27/04/2014 return lots of tracks so maybe my above diagnosis is wrong and something else is happening. If I filter on 30/04/2014 (today) I get tracks I've played earlier as well as some of yesterdays; If I filter on 01/05/204 (tomorrow) I get tracks I've listened to today, *all* of which are also included in the 30/04/2014 filter (which seems very odd to me) Reproducible: Always
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Yes I'm still seeing this - set last play 11/11/2018 and I get tracks played yesterday
Changing back to REPORTED per request of Myriam (Amarok dev).
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!