php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #78962 [bugsnet] Inconsistencies with Bug Report Statistics
Submitted: 2019-12-14 22:25 UTC Modified: 2022-01-20 17:20 UTC
From: austincmartorano at gmail dot com Assigned: cmb (profile)
Status: Wont fix Package: Website problem
PHP Version: Irrelevant OS: Irrelevant
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
MUST BE VALID
Solve the problem:
30 + 36 = ?
Subscribe to this entry?

 
 [2019-12-14 22:25 UTC] austincmartorano at gmail dot com
Description:
------------
Hello,
I was reading through the statistics page found here, https://bugs.php.net/stats.php , for a report I am writing regarding the closure rate of bug reports on this Bug Database. While recording these numbers, I found some inconsistencies between the columns. For instance, at the time of writing this documentation problem report the left most number column in the "All" row is listed as 78609 for total reports. However, when added all the columns after the total column, "Closed", "Open", "Verified", etc. the combination of all columns only sums to 78112. These two numbers should be equal given there is not missing data or another unlisted amount of bugs. I am mainly writing this for clarification on if there is a missing column or if another error may have caused this inconsistency. While writing this documentation problem report I would like to draw attention to a website problem reported some months back regarding the definition of the "Critical" status, Bug #77528. The current state of the statistics page gives the appearance of no "Critical" bugs as to see what would meet the qualification to receive the "Critical" status. So I also request a description of "Critical" and that it receive its own status field requested previously by Bug #77452. Thank you for your time reading my report.
Austin C Martorano

Test script:
---------------
Listing Number to show where I received the total value of 78112.
Closed: 37347 Open: 4193 Critical:N/A Verified: 367 Analyzed: 87 Assigned: 277
Feedback: 8 No Feedback: 6477 Suspended: 620 Not a Bug: 24385 Duplicate: 1329
Wont Fix: 3022
(37347+4193+367+87+277+8+6477+620+24385+1329+3022 = 78112)
Total Given From Statistic Table: 78609
78609 =/= 78112


Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2019-12-16 10:07 UTC] cmb@php.net
-Summary: Inconsistencies with Bug Report Statistics +Summary: [bugsnet] Inconsistencies with Bug Report Statistics -Status: Open +Status: Verified -Package: Documentation problem +Package: Website problem
 [2019-12-16 10:07 UTC] cmb@php.net
The difference might be due to tickets with status "spam", which
are apparently not listed.
 [2019-12-29 12:47 UTC] cmb@php.net
-Type: Documentation Problem +Type: Bug
 [2022-01-20 17:20 UTC] cmb@php.net
-Status: Verified +Status: Wont fix -Assigned To: +Assigned To: cmb
 [2022-01-20 17:20 UTC] cmb@php.net
Given that bugsnet has been superseded by GH issues, it is
sufficiently safe to assume that this issue won't be fixed.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Tue Mar 19 02:01:28 2024 UTC