Open Bug 1762360 Opened 2 years ago Updated 2 years ago

Drop QA Contact field

Categories

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

Product:
bugzilla.mozilla.org
Component:
Administration
Type:
task

Tracking

()

People

(Reporter: marco, Unassigned)

References

(Blocks 1 open bug)

Details

I've noticed the field is often wildly outdated. I was thinking we could detect inactive/disabled QA contacts with autonag and remove them or nag about them, but if this field is actually not used anymore maybe we can drop it or disable it?

Nobody seems to be using this field actively. No QA team is using it.

David, could we drop it?

Flags: needinfo?(dkl)
Summary: Consider dropping QA Contact field → Drop QA Contact field

Looking at https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&v1=2022-01-01&f1=qa_contact&resolution=---&o1=changedafter, it doesn't seem to be used much if at all. I'm asking around.

Note this query only shows when it was changed; this isn't a field that I would expect to be updated frequently.
There are 120 active components with a default QA field set.

Nobody seems to be using this field actively. No QA team is using it.

Which teams did you reach out to? QA-Contact is a Bugzilla-wide field, not per-product, so we need to ensure that all teams are ok with it being dropped.

Looking at the list I want to make sure you've reached out to the following teams who have a QA-Contact set on multiple of their components:

  • Bugzilla (the project, not BMO)
  • Infrastructure & Operations
  • Cloud Services
  • Data & BI Services Team
  • Mozilla Localizations
  • Release Engineering
Flags: needinfo?(dkl) → needinfo?(mcastelluccio)

For Infrastructure & Operations, dhouse confirmed they are not using it.

For Cloud Services, jbuck confirmed they are not using it.

For Data & BI Services Team, cvalaas said they are not really using Bugzilla.

There will be an impact to all existing components with a default QA-contact field - they will stop getting automatic visibility and notifications of all bugs in their component. Component watching is a close proxy for this, however QA-contact has the benefit of gaining visibility of security bugs in components even if the user isn't a member of the security group.

Perhaps existing QA-Contact users which are real users should be switched to being Triage Owners of the component instead?

For Mozilla Localizations, flod said for new components he's setting himself as triage owner. He's fine if we drop the QA Contact field and move himself from QA Contact to Triage Owner in components where he's currently QA Contact.

For Bugzilla, justdave mentioned they are not using the field.

For the rest of Infrastructure & Operations, johnb said he's set as QA Contact so he's automatically added to all bugs. He said he'd be fine with being triage owner instead, or switching to use the component watching feature.

For RelEng, Cyrus confirmed nobody in the team is using it.

Flags: needinfo?(mcastelluccio)
You need to log in before you can comment on or make changes to this bug.