where 999999 represents bugs open more than 2700 years, and we should take a while to reach that limit. The original code is in config_defaults_inc.php for anyone that would submit a "permanent" change.
I added the following code to separate the number of issues by the number of days open. Specifically, the value in "1" is the number of bugs open for 1 day or less. The value in the "2" row is the number of bugs open for 2 days or less. The issue I ran into was that a bug can exist in both instances.
The following code addresses this concern and separates the counts into their respective buckets:
The function summary_print_by_date has been copied here in its entirity as modified on my system (1.0.0rc2). I added 3 lines to this function noted by the "# -- Added" comment.
The code above goes in the "summary_api.php" file.
It is intended to separate the entries under the "By Date (days)" heading on the "summary_page.php" page as described. It is meant to change the filter so that instead of, for instance, producing a list of all bugs logged withing the last 30 days it will only yield a list of bugs logged between 30 days and the date range next to it.
However, for instance in my example below, when i click on the "13" which should be the number of bugs logged 2 days ago, i get a list of 23 bugs which include bugs logged over the last three days (today, yesterday and the day before yesterday). So it doesnt look like the filter made it into the link.
By Date (days)
1 10 => produces a list of 10
2 13 => produces a list of 23
3 12 => produces a list of 35
7 76 => produces a list of 111
30 182 => produces a list of 293
60 88 => produces a list of 381
90 66 => produces a list of 447
180 197 => produces a list of 644
365 418 => produces a list of 1062
9999 2074 => produces a list of 3136