User's reporting stats [1] are limited from left by version's start date. While this is correct, it causes that some relevant issues are not on the page. For instance issue 210136, which was reported before start date of 7.3.

Resolving statistics are not having this problem as they consider when bug was resolved, not created. 

I'm not sure how/if even this could be resolved. Several ideas:
- add another search for issues reported before version's start date, that have NO(version-1) => this could be very expensive as there is no bottom limit and next these results would have to been either merged with current results or probably easier (and faster) displayed separately on user's page. Also some way to determine keyword NO(version-1) would be needed. OTOH there'll be issues w/o this keyword as well so this would not help

- instead of looking for NO(version-1), find all reported issues in period e.g. version's start date - 3 months => again not a solution for old issues

- since the issue is mainly for verifying, add a new table column called "old not verified" that would search for all reported issues in date (0 to version's start date) that are resolved and not verified. This search could be relatively cheap, there is a lot of search criteria and I think it would not need any join or similar expensive sql query. Plain select from one table. These new data would not be considered in any statistics, their only purpose would be to give user a link to BZ with these issues

- ignore these issues? Probably not a good idea, they should be still verified



I'll do #3 and let's see how expansive would it be.





[1] quality2.netbeans.org/dashboard/web/user.php?username=vriha&version=7.3