Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 474490 - [server] Add ability to sort problems by the number of reporters
Summary: [server] Add ability to sort problems by the number of reporters
Status: CLOSED FIXED
Alias: None
Product: EPP
Classification: Technology
Component: Automated Error Reporting Client (AERI) (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: later   Edit
Assignee: EPP Error Reports CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 474514
  Show dependency tree
 
Reported: 2015-08-07 06:38 EDT by Szymon Ptaszkiewicz CLA
Modified: 2015-08-10 05:40 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Szymon Ptaszkiewicz CLA 2015-08-07 06:38:39 EDT
It would be very nice to have an option to sort problems by the number of reporters. Right now we are able to sort by the number of incidents but this does not correspond well to the number of reporters - there are a few cases where problems with thousands of incidents were reported by a handful of people which indicates those problems are probably less harmful than those with the same number of incidents but reported by more users. Having the ability to sort by the number of reporters would allow us to easily see problems that affect wider audience and then tackle them with higher priority than other problems.
Comment 1 Marcel Bruch CLA 2015-08-08 13:45:42 EDT
I've enabled sorting by number or reporters.
Comment 2 Szymon Ptaszkiewicz CLA 2015-08-10 04:47:54 EDT
(In reply to Marcel Bruch from comment #1)
> I've enabled sorting by number or reporters.

What happened with sorting by number of incidents? Right now, I see there is even no column which shows number of incidents. My intent was not to replace sorting by incidents with sorting by reporters but to allow both options, like in bugzilla's search where we can use either Severity or Priority (or combination of the two).
Comment 3 Marcel Bruch CLA 2015-08-10 05:02:33 EDT
Did you find that useful? I had the impression that it's basically a weak substitute for sorting by the number of reporters.

what you can take away from the number of incidents is: if it's much higher than the number of reporters, then there are quite many ways how this problem can be produced. But I don't feel this is very helpful.

Keep in mind: a client sends the very same error report *only once* per workspace (to save network resources and reduce annoying error popups on client side). It's thus not useful as a measure how often a single users experiences this issue. But I think this can be substituted by the number of error reporters.
Comment 4 Szymon Ptaszkiewicz CLA 2015-08-10 05:10:39 EDT
(In reply to Marcel Bruch from comment #3)
> Did you find that useful? I had the impression that it's basically a weak
> substitute for sorting by the number of reporters.

I did find it useful but I believe merely due to its sorting ability. Based on your explanation above I think we are good right now. Thanks for fixing it!