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
While going through all my needinfos on Bugzilla, I realized a good chunk of them were on closed bugs.
One of the most common pattern is needinfo added on backed out patches, for which I fixed the issue and land the bug again, but forget to clear the needinfo.
I saw other cases where I was asked something , and someone else replied, which "unlocked" the bug so it was fixed later.
Having a small comment that would say something like "The bug was closed and has a needinfo for you. Clear the needinfo if it's not relevant anymore"
The text was updated successfully, but these errors were encountered:
Thank you for filing the issue. Commenting on the bug itself could introduce some noise since this will trigger emails to all people in the CC. Alternatively, we could have the bot send an email with the list of all bugs that match the closed bugs that have needinfo on you.
Commenting on the bug itself could introduce some noise since this will trigger emails to all people in the CC. Alternatively, we could have the bot send an email with the list of all bugs that match the closed bugs that have needinfo on you.
Sure! I was thinking of a comment as it would send a bugmail, so having the email directly without adding noise on bugzilla sounds good to me 👍
While going through all my needinfos on Bugzilla, I realized a good chunk of them were on closed bugs.
One of the most common pattern is needinfo added on backed out patches, for which I fixed the issue and land the bug again, but forget to clear the needinfo.
I saw other cases where I was asked something , and someone else replied, which "unlocked" the bug so it was fixed later.
Having a small comment that would say something like "The bug was closed and has a needinfo for you. Clear the needinfo if it's not relevant anymore"
The text was updated successfully, but these errors were encountered: