Closed Bug 1527001 Opened 1 year ago Closed 6 months ago

Analyze duplicated, underused or misused bug fields

Categories

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

Production
task
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: kohei, Assigned: kohei)

References

(Blocks 2 open bugs)

Details

(Keywords: bmo-ux)

Attachments

(1 file)

We have various redundancy and inconsistency issues due to too many bug fields and values. Some of them are being solved by the autonag bot but I’d like to list everything here. The weirdest thing for me is, as tweeted before, the ASSIGNED status overlapping with the Assignee field.

Status: NEW → ASSIGNED
See Also: → 1525202
See Also: → 1525376
Summary: Analyze duplicated and underused bug fields → Analyze duplicated, underused and misused bug fields
See Also: → cleanup-bugzilla
Summary: Analyze duplicated, underused and misused bug fields → Analyze duplicated, underused or misused bug fields

My draft doc is on Google Docs. Will make it public later.

Adding discussion on bug lifecycle from end of 2018.

Attachment #9043444 - Flags: feedback?(kohei.yoshino)
Comment on attachment 9043444 [details]
Rethinking Bug Lifecycle Document

Yeah I still remember this doc, but looks like we haven’t reached any conclusion yet. We need to continue discussing it.
Attachment #9043444 - Flags: feedback?(kohei.yoshino) → feedback+
See Also: → 1534025
Blocks: 1534025
See Also: 1534025
Blocks: 1525376
See Also: 1525376

The reorganized modal modules helps better understand duplicated fields.

Depends on: 1344091
Type: enhancement → task
See Also: → 1563611
Status: ASSIGNED → RESOLVED
Closed: 6 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.