Open Bug 1729270 Opened 3 months ago Updated 2 months ago

When changing severity from -- to something, bugzilla complains that a comment is needed

Categories

(bugzilla.mozilla.org :: Bug Creation/Editing, defect)

Production
defect

Tracking

()

ASSIGNED

People

(Reporter: lth, Assigned: dkl, NeedInfo)

References

(Regression)

Details

Attachments

(1 file)

46 bytes, text/x-github-pull-request
Details | Review

This looks like a new thing: when changing severity from nothing to something, bugzilla now complains that a comment is required before the bug can be saved.

This does not seem like the right thing, and will probably stop people from changing severity at all during normal incoming-bug triage. (Certainly I will stop.)

Assignee: charting → nobody
Component: Reporting/Charting → Bug Creation/Editing
Product: Bugzilla → bugzilla.mozilla.org
QA Contact: default-qa
Regressed by: 1690201
Version: unspecified → Production

We ran into this in our triage meeting: It would be nice if this would be at least loosened up a bit:

  • Bugs which are Enhancements/Tasks can be set to severity N/A, and this should be allowed without comment.
  • Personally, I'd argue S3/S4 should also be allowed without comment.

This change was part of a set of changes implemented to help triage.
As the driver for these changes is on extended leave I'll see if I can find someone else to make the call here.

Flags: needinfo?(glob)

One problem here is requiring the comment when changing severity of Enhancement bugs, those usually don't have severity and having to copy paste "Severity N/A because it's an enhancement" is not great.
The other thing is the added work necessary when triaging from -- to S3, I would be fine having to provide a reason to change something TO or FROM S1 and S2. S3 and below are very common changes instead and not so critical.

(In reply to Lars T Hansen [:lth] from comment #0)

This does not seem like the right thing, and will probably stop people from changing severity at all during normal incoming-bug triage. (Certainly I will stop.)

FWIW, as a triage owner, I also don't see myself setting the severity going forward. If anything I might copy and paste the strings from https://wiki.mozilla.org/BMO/UserGuide/BugFields#bug_severity. That's just not good use of my time.

glob, what's the latest here?

I'm still trying to find an owner for the Firefox triage process (not helped by various bouts of PTO).

I agree that this particular issue is painful and needs tweaks in its current form.

We'll disable requiring a comment completely until we (a) find an owner, and (b) this requirement has been tweaked based on the feedback here.

Attached file GitHub Pull Request
Assignee: nobody → dkl
Status: NEW → ASSIGNED

Fix merged to master to disable this for now.
https://github.com/mozilla-bteam/bmo/commit/fe410ce416f65b5290acd9a7a99c88c5d42385f1

Leaving bug open for more feedback.

You need to log in before you can comment on or make changes to this bug.