Last modified: 2014-08-14 11:47:12 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T71179, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 69179 - Remove severity related graphs from bugzilla_response_time.html
Remove severity related graphs from bugzilla_response_time.html
Status: RESOLVED FIXED
Product: Analytics
Classification: Unclassified
Tech community metrics (Other open bugs)
unspecified
All All
: Low enhancement
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-08-06 13:32 UTC by Andre Klapper
Modified: 2014-08-14 11:47 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Andre Klapper 2014-08-06 13:32:06 UTC
Having used http://korma.wmflabs.org/browser/bugzilla_response_time.html for a while, Quim and I have realized that severity is less meaningful than priority (related discussion about the usefulness of a Severity field can be found in http://fab.wmflabs.org/T168 ) - for example, a blocker or critical issue in a way less used code area is more likely to sit dormant for a while (and might require volunteer efforts to get things going), which is not a problem per se.

Hence proposing to remove those three severity related graphs, to have less graphs to concentrate on.
Comment 1 Quim Gil 2014-08-13 12:53:01 UTC
This should do it.

https://github.com/Bitergia/mediawiki-dashboard/pull/52
Comment 2 Santiago Dueñas 2014-08-14 10:02:52 UTC
Pull request merged.
Comment 3 Quim Gil 2014-08-14 11:47:12 UTC
Thank you!

The changes are visible at http://korma.wmflabs.org/browser/bugzilla_response_time.html (you might need to refresh the cache of your browser).

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links