2022.7: A stunning performance

That’s fair. I tried to be clear I was suggesting a temporary workaround not a long-term solution, I don’t think users should have to rebuild what they had with a custom card either.

That being said I could get behind this being a bug rather then an FR. Particularly if you added include and exclude filters to history. In that case create an issue here.

Bear in mind here that changes (particularly to the frontend) rarely (if ever) make everyone happy. The general feedback in the forum, discord and really all channels I had seen is that the history panel was not useful for people. It was slow and unwieldy and required a massive amount of effort to make it not that so more people ignored it then used it. I know I was one of those people. I tolerated it since it was the only easy way to view a particular entities history in a dynamic date range until I found history explorer then I tossed it immediately.

This isn’t to dismiss your feedback at all. Like I said above, if you did spend the effort to configure includes and excludes those should be acknowledged and be the default filters IMO. Just that the goal was to make history useful OOTB for the most people with minimal configuration and I personally think this change accomplishes that well.

2 Likes