We recently noticed that when we loaded our dashboard, the "20 recent issues" table will only display some number of less-than 20 issues.
While troubleshooting this we increased the value of the PHP includes from 20 to 40, so now the table is "40 most recent issues". After this we noticed that the number of issues actually displayed in the table is always a number equal to ( N - 12 ) where N is the number that the dashboard is reporting that it shows.
For example, if the dashboard table shows "27 of 27 issues" then the table actually displays 15 issues, not 27.
We looked at the response for the POST to /dashboard.php with the body "favobj=hat&favref=hat_lastiss&favaction=refresh&_ =" and, in fact, the table string in the response only contains the table data for the issues shown, leading us to start investigating the code in dashboard.php.
As we continue to investigate this issue, does anyone have any idea how to go about resolving this issue? We suspect that this could be a problem with duplicate host names in the database since we discovered that the REST API will allow you to insert duplicate host names, but we haven't identified a root cause for this behavior yet.
Thanks in advance.
While troubleshooting this we increased the value of the PHP includes from 20 to 40, so now the table is "40 most recent issues". After this we noticed that the number of issues actually displayed in the table is always a number equal to ( N - 12 ) where N is the number that the dashboard is reporting that it shows.
For example, if the dashboard table shows "27 of 27 issues" then the table actually displays 15 issues, not 27.
We looked at the response for the POST to /dashboard.php with the body "favobj=hat&favref=hat_lastiss&favaction=refresh&_ =" and, in fact, the table string in the response only contains the table data for the issues shown, leading us to start investigating the code in dashboard.php.
As we continue to investigate this issue, does anyone have any idea how to go about resolving this issue? We suspect that this could be a problem with duplicate host names in the database since we discovered that the REST API will allow you to insert duplicate host names, but we haven't identified a root cause for this behavior yet.
Thanks in advance.