This issue has apparently been “known” since 2016. It has frustrated me since at least 2022.
Edit: A Roon founder commented in December of 2022 that there are plans to fix it, but when?
Edit 2: A year later, Roon technical support closed the thread after stating that a ticket is in the dev queue. Again, when will this be fixed? How many more years?
Other options available (Plex Media Server in use with Symfonium) have play count and last played date:time.
If an album (or track) is played greater than 99% (can be changed) it shows under play count, if you just play part of it, it will just update the date:time.
So this seems possible and easy to implement 
Yes this has been bothering me since way back even though today I mostly choose to ignore this. But it’s quite bizarre that it has not been fixed yet - even after multiple tickets and reports that it would be worked on.
It’s the way of Roon 
I think that Plex/Symfonium implementation is brilliant
Edited by user 
Hi @tretneo,
Your frustration is very much warranted! I can confirm we still have a development ticket in the pipeline, but the fix is complex, and progress has very clearly been much slower than we had hoped.
I wish I had more to share, or had a workaround to give you, but unfortunately, there isn’t much we can do until we push an official fix.
@Mr.Flibble as you know, better than most Roon Community members, we very much welcome personal thoughts and opinions. However, Technical Support threads are not the place for them. At this point, this shouldn’t need repeating. Unless you’re offering a troubleshooting step or a Roon-related solution, please consider posting elsewhere.
I understand this particular issue has been long-standing and lacks a solid workaround, and I do resonate with your frustration. Still, please remember the community guidelines you’re certainly familiar with by now. Thank you 
Thank you for your reply, @benjamin. I do appreciate your candid response. I get that you can’t make commitments, and technically it sounds like the issue is still “open”, but at this point I’d almost rather hear something like, “We won’t fix this.” At least that way there’s a solid expectation and no more hoping in vain.
Hi @tretneo,
We will keep this thread open to track the issue and the team can give updates on the ticket’s progress. It doesn’t look like there’s currently an active tracking thread for this issue, which no doubt compounds the lack of transparency.
It looks like @benjamin gave a clear sense of timeline expectations. That said, it’s not our intention to abandon this issue. The team will share information as it becomes available.
Hello @tretneo
We will keep you posted with any updates available.
When should we expect an update?
Hello. As @benjamin suggested, there’s a chance that Roon users (at least the technical experts) might be able to contribute helpful hints or even a solution to the problem. Roon was never public domain – so how is that possible without knowledge of the system design - or did I get it wrong?
/Geefes
I think you did, I just reread @benjamin’s post and I don’t see what you’re suggesting.
Reading back on this it seems Roon are aware and know how to fix it, but it’s a very complex architecture change (effort & risk) … I guess it boils done to their priorities.
That said a fix for this is well over due.
