1522340 - (new-bug-type) [meta] Clear definition of defect vs. enhancement vs. task in Firefox-related components

Status: RESOLVED FIXED

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

Description

[Emma Humphries ☕️🎸🧞‍♀️✨ (she/they) [:emceeaich] (Pacific Time) use needinfo]

It is unclear what is a defect vs. a task vs. an enhancement in Bugzilla.

We have keywords (meta, and feature) and the enhancement severity, as well as starting bug summaries with [meta].

These are used inconsistently, and inflate the amount of work engineering needs to do to manage bug triage.

We need a standard.

We propose adding a three value field to Bugzilla (and optionally to upstream if they wish to take it) indicating if a bug is:

• A defect (regression, crash, security issue, …)
• An enhancement (new feature, UI improvement, enhancement)
• A task (refactor, remove, replace, enable, disable)

This is a meta bug for the work, and we'll capture the changes necessary for this work as blockers.

By engaging in this project we plan to accomplish:

• Making it clear what is a bug to triage, versus what's a task or enhancement
• Make our triage backlog reporting clearer
• Reducing the triage workload by excluding non-defect work
• Making it easier to file bugs reflecting intent

Comment 1

[Sylvestre Ledru [:Sylvestre]]

Thanks Emma, this is going to be a great step!

Comment 2

[Kohei Yoshino [:kohei]]

Updating the bug summary as the feature type has been renamed to enhancement.

Comment 4

[Mark Clements]

(In reply to Emma Humphries, Bugmaster ☕️🎸🧞‍♀️✨ (she/her) [:emceeaich] (UTC-8) needinfo? me from comment #0)

We propose adding a three value field to Bugzilla (and optionally to upstream if they wish to take it) indicating if a bug is:

Given that bug 9412 has been made a duplicate of this bug, it appears that this update has been accepted upstream and will make it into the official Bugzilla release. Is that correct?

Some questions:

1. Is the set of options field going to be editable for downstream users?
2. Will automatic migration be included for existing installations?
3. Are there any other considerations with regards changing the initial Mozilla solution into a general Bugzilla solution?

Comment 5

[Kohei Yoshino [:kohei]]

(In reply to Mark Clements from comment #4)

Given that bug 9412 has been made a duplicate of this bug, it appears that this update has been accepted upstream and will make it into the official Bugzilla release. Is that correct?

Yes, this comes with Bugzilla 6.0 which will be based on BMO.

1. Is the set of options field going to be editable for downstream users?

Yes. The types, defect, enhancement and task by default, are editable.

2. Will automatic migration be included for existing installations?

No. Each installation could have their own migration plan depending on their needs. Mozilla uses both a component-based migration script and machine learning for the migration that will happen in a few days.

3. Are there any other considerations with regards changing the initial Mozilla solution into a general Bugzilla solution?

Currently the design of these 3 types are hardcoded in the stylesheet so you have to do the same if you’d like to add or change the types. In the future, it will probably be able to specify the colour and icon for each type on the admin page.

Comment 6

[Kohei Yoshino [:kohei]]

We made it!