mantisbt:summary_by_activity
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| mantisbt:summary_by_activity [2007/07/31 04:32] – created giallu | mantisbt:summary_by_activity [2011/11/16 07:42] (current) – The page rendering was broken (maybe since new PHP version on mantisbt.org). Added new line to fix it at end of file. atrol | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| ===== Rationale ===== | ===== Rationale ===== | ||
| - | The summary page could benefit from a list of the most active bugs; for the implementation of this feature several | + | The summary page could benefit from a list of the most active bugs, since active bugs are likely related to topics |
| + | |||
| + | Several | ||
| - the number of views of the given bug (currently, this data is __not__ available in mantis) | - the number of views of the given bug (currently, this data is __not__ available in mantis) | ||
| - the number of monitors | - the number of monitors | ||
| - the number of bugnotes | - the number of bugnotes | ||
| + | - the number of attachments | ||
| + | |||
| + | ===== Implementation ===== | ||
| + | |||
| + | The current implementation leverages the bug_history_table content to score the bugs and build the top ten list; this looks like the easiest way to take into account all of the above metrics (of course excluding bug views) | ||
| + | |||
| + | * Each history entry weights as 1 point | ||
| + | * only open bugs (e.g, with state below the resolved threshold) are listed | ||
| + | |||
| + | Of course we could refine the scoring function to give " | ||
| + | |||
| + | * weights more monitor events | ||
| + | * weight more has_duplicate events | ||
| + | * give negative weight certain events (unmonitor) | ||
| + | |||
| + | and/or provide a custom function hook to personalize the scoring function | ||
| + | |||
| + | |||
mantisbt/summary_by_activity.1185870758.txt.gz · Last modified: (external edit)
