115177 - Ability to disable/enable QA Contact field per component

Status: NEW

(Bugzilla :: Administration, task)

Description

[John Vandenberg]

QA personnel are not always required/available for all components of a product,
or a different product may not wish to use exercise QA via Bugzilla.  Whilst the
QA contact could be set to a fake address, it then wastes space on the bug form.

Following on from bug #14461, if the QA contact is 'missing', then new bugs do
not get assigned a QA contact.  Capitalising on the fact that only components
with no default QA will have new bugs without one, if the bug form detects there
is no QA contact, Bugzilla can hide the QA field.

Comment 1

[John Vandenberg]

Attachment: Hides QA field if component has no default QA

This patch depends on Bug #14461 otherwise its not to useful.

Comment 2

[Dave Miller [:justdave]]

Maybe we should add a field to the component editor to specify whether or not
the component uses a QA contact, instead of depending on there being a default
QA.  I think it's conceivable that you might want to allow QA contacts on a
product but not have a default one.  But I do agree that whether or not to have
a QA contact should be a component-level option.

Moving a bug into a component that doesn't use one should clear it, too,
otherwise you'll get confusing results on queries...

Probably an option to to *require* a QA contact would go along with this well,
then moving a bug into a component that required one would prompt you for a name
or to use the default.

Comment 3

[John Vandenberg]

Should a component require use of the QA contact field, a nobody account can be
specified as the default QA.  I agree that bugs that move should have various
fields modified to conform to the new component, however if the QA field is
retained, this patch will keep it visible even if the component doesnt normally
display a QA contact field.

Comment 4

[Matthew Tuck [:CodeMachine]]

Using nobody accounts is a hack.  Requiring a QA isn't a bad thing, it would be
as much for people sanity checking their actions as to prevent people doing bad
things.

Comment 5

[Matthew Tuck [:CodeMachine]]

Also if an admin doesn't have create a nobody account it can't be used.  And
nobody accounts only exist in the first place because assignees don't also work
in the way described above, which they should.

Comment 6

[Bradley Baetz (:bbaetz)]

Comment on attachment 61689 [details] [diff] [review]
Hides QA field if component has no default QA

This won't apply because of the templatisation

Also needs the changs in justdave's comment #2

Comment 7

[Joel Peshkin]

Unloved bugs targetted for 2.18 but untouched since 9-15-2003 are being
retargeted to 2.20
If you plan to act on one immediately, go ahead and pull it back to 2.18.

Comment 8

[Gervase Markham [:gerv]]

I think the only sane way to implement this is to hide the field if there's no value _and_ no default. If we hide it simply when there's no default, what do you do when a bug moves component? Have a hidden and uneditable QA person? Or silently remove them from their job? If we hide it when there's no value, then how do you set a value? If you hide it only in certain components, who maintains that list without extra UI?

If this were ever done, we should add a class to the qa_contact container <div> or whatever if those conditions are true, then people can use that to hide it if they wish. But I suspect this bug will never be fixed, because no-one actually needs this apart from the guy who reported in 12 years ago.

Gerv