-
Notifications
You must be signed in to change notification settings - Fork 310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MEI: Have a measure of incoming/closed defects vs. existing open #3715
Comments
jensstutte
changed the title
Have a measure of incoming/closed defects vs. existing open
MEI: Have a measure of incoming/closed defects vs. existing open
Oct 13, 2023
@jensstutte two questions:
|
(Edit: misconception on my side) |
(it might be nice to have links in the mail that open a query showing those bugs?) |
marco-c
added a commit
to marco-c/bugbug
that referenced
this issue
Oct 13, 2023
marco-c
added a commit
to marco-c/bugbug
that referenced
this issue
Oct 13, 2023
marco-c
added a commit
to marco-c/bugbug
that referenced
this issue
Oct 13, 2023
marco-c
added a commit
that referenced
this issue
Oct 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Based on this doc.
Given that
NumOpenDefects(Start(TimeInterval))
is hard to query live, we estimate it by:such that if the calculation is run with an end date of the time interval that is close to today we can use the up-to-date values for components and severity without bothering too much for deviations.
The text was updated successfully, but these errors were encountered: