Closed Bug 1480097 Opened 6 years ago Closed 6 years ago

Add a 'stalled' keyword for bugs that progress is blocked on until more info is available

Categories

(bugzilla.mozilla.org :: Administration, task)

Product:
bugzilla.mozilla.org
Component:
Administration
Version:
Staging
Type:
task
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: jesup, Assigned: emceeaich)

Details

This is to allow filtering of non-currently-actionable bugs that still exist. We don't want to close them, but we've been unable to make progress on them until some new information is available. This isn't for garden-variety "waiting on reporter" type of stuff, but bugs that we've run out of paths to explore. In particular, this is meant for bugs found in the field via crashreporter and the like, which often are hard to make progress. This is especially useful for sec bugs, and can be used in reporting there Could be stalled, or even sec-stalled, or have both. I recommend 'stalled'
I can this, but I wanted to run it by Emma first. Emma: Does this mesh okay with your stuff?
Assignee: nobody → dylan
Flags: needinfo?(ehumphries)
We have a "keep-open" keyword. Would this be different than that? I'd rather have a keyword than a whiteboard tag for all this.
Flags: needinfo?(ehumphries) → needinfo?(rjesup)
(In reply to Emma Humphries, Bugmaster ☕️🎸🧞‍♀️✨ (she/her) [:emceeaich] (UTC-8) needinfo? me from comment #2) > We have a "keep-open" keyword. Would this be different than that? My understanding of the "leave-open" keyword, is to prevent sheriffs from closing a bug once it has landed on mozilla-central, because someone expects to continue working on the bug after. Having a "stalled" or "non-actionable" keyword / status flag would be used to filter out bugs from triage lists, until we get either new data or new ideas to make them actionable again.
Right - this is different than leave-open. That handles things like "I want to land a diagnostic patch to get more info for this bug" or "I have a partial fix for this and more parts will come later". And yes, it should be a keyword.
Flags: needinfo?(rjesup)
Okay, then I want to create some language and shared understanding around this. I'll draft documentation for the how to triage bugs page, and a communication on it.
Flags: needinfo?(ehumphries)
I've asked the triage leads mailing list about this and will proceed with the keyword and the change to the the "to be triaged" dashboard after waiting for feedback.
Flags: needinfo?(ehumphries)
Also, I plan to use "This is a bug for which we cannot take further action without more information. The reporter has shared all they know with us. This bug should be kept open, but for now we are out of strategies to take to resolve it. The priority of stalled bugs should be '--' but other keywords may apply to them." as the keyword description.
Flags: needinfo?(rjesup)
SGTM
Flags: needinfo?(rjesup)
As I'm about to leave for Worldcon, I don't want to push changes to keywords or triage queries live. I've a pull request open for the triage query change at https://github.com/emceeaich/are-we-triaged-yet/pull/52 and will make both changes on the 20th.
Note to do this when I return.
Flags: needinfo?(ehumphries)
I've updated the query in AWTY, added the keyword, and updated triage documentation.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(ehumphries)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.