Mass change of bugs with inactivity for 1 year

[Patrick Brosset]

If you are not on the firefox-dev or dev-platform mailing lists, you may
not be aware of this, but might have seen a large amount of bugs'
resolution state changed recently.

Here's more information about the change:


1.

Introducing an ‘Inactive’ state as a bug resolution in Bugzilla
2.

Moving tickets that haven’t been modified in 12 months to ‘Inactive’
3.

The query excluded P1 bugs and included Firefox-related products
4.

Why did we do this? To balance the signal:noise ratio in Firefox
Bugzilla searches


I just ran a query on all DevTools bugs to see which ones had been resolved
as inactive and it turns out more than 3000 have.
Many of these bugs are very much valid. They're still in the database of
course and can still be found, but they are now marked as resolved. I think
this is wrong and should be reverted.

There's discussion at the moment occurring on firefox-dev about that. So
please join the conversation there if you wish.

In the meantime, here's what has been suggested so far:


-

If this mass-modify
<https://bugzilla.mozilla.org/show_bug.cgi?id=1445054> has disrupted
your workflow to the point you need to a virtual ‘undo’ button, please file
a ticket
<https://bugzilla.mozilla.org/enter_bug.cgi?product=bugzilla.mozilla.org&component=Administration>and
we will work with you to repair your workflow. Your bugs will be back to
the ‘Active’ state as quickly as possible if that is what you require.
Otherwise, we can evaluate what action is needed on a case-by-case basis.

[Patrick Brosset]

Here's the DevTools query: https://mzl.la/2xaoaBL
Be prepared to wait a bit, this is the unlimited query, so it will take
some time to load.

On Fri, May 25, 2018 at 12:13 PM, Patrick Brosset <pbro...@mozilla.com>
wrote:

[Patrick Brosset]

I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1464397 to ask for a
revert.