| Summary: | The default for the field "Documentation Change" is not really a default. | ||
|---|---|---|---|
| Product: | [Infrastructure] Bugzilla | Reporter: | Igor Stoppa <igor.stoppa> |
| Component: | bugzilla | Assignee: | Michael Halstead <mhalstead> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | CC: | infras.bug.watcher, Infras.watcher, srifenbark |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Igor Stoppa
2015-06-01 12:26:12 UTC
Default in this case doesn't mean it is selected by default in the interface. It means this option should be selected by the user if no options are appropriate. If we changed the label to "Undecided or Not Applicable" would that clarify the selection? (In reply to comment #1) > It means this option should be selected by the user if no options > are appropriate. That smells like a real default to me :-D Chances are that if the reporter can really answer that question, (s)he also knows about the option and will set it anyway. For everyone else I think it would be just confusing. But you guys know how many bugs have that field set to something else than the pseudo-default ... if they are not too many, you could just make it a real default and be friendlier toward bug reporters :-) What I find really confusing is that there is that "(default)" in the option, but it still requires manual selection. Imho that "(default)" should just go away. If it's really default, make it so also from bugzilla perspective. If it's not default, drop the string which states otherwise. In the initial design we wanted people to have to make this decision when a new bug was opened. I've changed the label to hopefully be more clear. Perhaps we've had this in place long enough that we don't need people to choose an option anymore and can have "Undecided" as the default in the interface. Scott can you comment? Hi, To me, "Not Applicable" is equivalent to "No". I think you should have 4 choices here: 1. I don't know 2. No 3. Yes 4. Done "Undecided" implies that the user can't decide between "Yes" or "No". They do not understand whether a fix will impact the docs or not. I think it would be clearer if we just had a selection called "I don't know". "Undecided" could mean some some strange factor is keeping them from making a decision between "Yes" and "No". A person that files a bug will either understand if a doc change is needed or not. If not, they don't know. I think it is fine that Bugzilla still complains if you don't put a choice in for the doc flag. There should be no default for this flag IMO. I think we need some awareness also on how to use this flag in the bigger picture. Example, a bug gets filed for some issue and the assignee is some engineer. The flag for docs is set to "Yes". The engineer researches and implements a fix. Maybe QA even looks at the fix (maybe not, either way would work). At that point, the bug should be assigned to the doc person since that part of the fix is still missing. Once the doc part is fixed then it can be set to RESOLVED. That is my opinion. Scott Updated choices to include "Don't know". Please let me know if the new option label causes any trouble. What does the "--" mean from the doc flag pull down? |