Maybe there's situations where it'd be useful to see a list of all of the suggested bugs when we have more suggestions than max_limit? If it's just a situation where we have a really common crash signature or something in multiple test files, we'll get more than 20 suggested bugs. If the user is presented with a list of them, maybe we could find a bunch of these and combine them into a single bug, bringing the number down below 20.
Comment on attachment 8770820 [details] [review] [treeherder] KWierso:maxlink > mozilla:master I am not attached to this at all, happy to close this if no one likes it, but here it is nonetheless.
If you check out this PR and run ./web-server.js, http://localhost:8000/#/jobs?repo=mozilla-inbound&bugfiler&tochange=f7a95ad1275001fa5ef8028fa557d89f6528ad43&fromchange=f7a95ad1275001fa5ef8028fa557d89f6528ad43&filter-resultStatus=testfailed&filter-resultStatus=busted&filter-resultStatus=exception&selectedJob=31581802 shows what it looks like and does.
Comment on attachment 8770820 [details] [review] [treeherder] KWierso:maxlink > mozilla:master I'm definitely not against giving people the option to view the list of bugs, however: * it's worth noting that it's capped at 50 bugs server-side (and in no particular order IIRC) - see: https://github.com/mozilla/treeherder/blob/66ea865de690528166a8de0f43d88ebe69e86575/treeherder/model/models.py#L147 * we shouldn't be making a second list of bugs to show - just use the original lists and adjust the logic for displaying them in the template
Tweaking bug summary - it's best to phrase them as definitive statements rather than questions/maybes - if we don't want to take a fix we can always WONTFIX bugs :-)