Closed Bug 1050252 Opened 10 years ago Closed 7 years ago

Provide checkboxes for "crash" and "hang" and "perf" keywords on final page of guided bug entry

Categories

(bugzilla.mozilla.org :: Extensions, defect)

Production
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: Gijs, Unassigned)

References

(Depends on 1 open bug)

Details

Sample text (which might need wording tweaks):


"This is a problem where Firefox crashes (exits unexpectedly)"

"This is a problem where Firefox gets stuck and I have to force-exit it myself"

"This is a problem where Firefox is really slow or uses too much memory"
Due Date: 2014-11-05
Assignee: nobody → dylan
Using the per-product products.js configuration, I'm going to add a keywords object
to products['Firefox']. Something like:

keywords: { crash: { text: "This is a problem where Firefox crashes (exits unexpectedly)", sort: 1 }, ...}

Then, on the bugForm step, we can just iterate over the keywords (if any) and add the associated checkboxes.
Status: NEW → ASSIGNED
This can go in as soon as the general guided bug layout code goes in (bug 1050232)
Due Date: 2014-11-05
I'm sitting on this until the improved layout bug is approved, as a decision in that patch drastically impacts how this one will work.
Great stuff. This is being done cross product, eg also for Thunderbird?

And, for crash and hang can you also set priority=critical, as they are such by definition?
(In reply to Wayne Mery (:wsmwk) from comment #4)
> Great stuff. This is being done cross product, eg also for Thunderbird?

For specific products -- there are a few things that work like this in guided bug entry.
I've made a note to apply it to TB.

> And, for crash and hang can you also set priority=critical, as they are such
> by definition?

Hmm, yeah I can do that.
Depends on: 1122127
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
why => incomplete?
Flags: needinfo?(dylan)
Assignee: dylan → nobody
Flags: needinfo?(dylan)
Component: Extensions: GuidedBugEntry → Extensions
You need to log in before you can comment on or make changes to this bug.