You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 4, 2019. It is now read-only.
For bugs with multiple signatures, it can be sometimes hard to evaluate the total number of crashes involved when they are scattered across a bunch of signatures with low crashes.
Your reasoning is correct when all the signatures in the bug are relative to the same root cause.
But sometimes a patch is fixing some signatures and not some others, so it means that the patch doesn't cover everything or the non-fixed signatures are another issue.
But I understand your point and maybe we could add a button or anything else to have global stats when the user want to have them.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For bugs with multiple signatures, it can be sometimes hard to evaluate the total number of crashes involved when they are scattered across a bunch of signatures with low crashes.
Here is a mockup of what it could look like
Example of bugs where it would be useful:
https://bugzilla.mozilla.org/show_bug.cgi?id=1464938
https://bugzilla.mozilla.org/show_bug.cgi?id=1465556
Maybe this could be triggered when the number of signatures is > 5
The text was updated successfully, but these errors were encountered: