Percival

This I think will be really useful, putting further limelight on a feature that is central to why members visits - or not - a Q&A-oriented community.
Something to consider about the statistics offered could be to complement with a basic way to show the spread of time to solution (e.g. the standard deviation). This would show if the time to solution in a forum is similar for most questions (like the fictive forum being red in the picture), or if some come members get answers with the speed of light and some have to wait painfully long (blue).
A measure of spread could indicate if there is an imbalance between the answers needed by members and the answers provided within specific knowledge areas. Combined with a way to identify the posts in the statistics shown (maybe the search function will do the trick) this could trigger rewarding actions to close this gap, increasing member satisfaction and strengthening the community brand. 
Posts never being marked as solved could be treated similarly, being able to identify and analyze so that appropriate action may be taken.
I'll add this idea to the Feature Suggestions forum when we have used the solution for a while.
 
 

Figure: Same mean value to solution but different spread.

That's a nice feature! 👌

That's a nice feature! 👌

Nice feature but i join all what it was said, is should be a native feature on all plans, cloud or self.
+1 for the feature -1 for the restriction 

It would be interesting to see how this would work on a mobile device! 
Everything always seems to be shown on a computer and never on a mobile phone when the majority of people will access most forums on a mobile these days 

I believe that your approach to the issue of links that contain ?do=find is not a good SEO solution. Providing a way to add entries to your robots.txt files is not a bad idea, but in reality just blocking Google from crawling these links, won't get rid of the biggest SEO problem that they create, and I don't believe that it's crawl budget...it's all of the 301 redirects that happen due to the fact that you use such links throughout IPS software.
I believe that the best solution is simply to rewrite your code (I had a custom plugin made to do this) so that the proper, final link is used, rather than a link containing something like ?do=findComment. If you write code that doesn't use a 301 redirect it will eliminate both issues. I also have a robot.txt entry for these as well, but that alone did not help the 301 redirect issue, which my SEM Rush account had already flagged as a critical fix for my site's SEO.

Performance improvements have been made across the board, including to the converters.