| Line 16: | Line 16: | ||
Resolution: Remove/hide or lock ( fields can be visible set to a certain value but none editable ) all unnecessary fields from the reporter in the bugzilla ui if a reporter does not belong to any group. ( if a reporter is in x group it might show and allow him to edited certain fields based on what that x group is ) | Resolution: Remove/hide or lock ( fields can be visible set to a certain value but none editable ) all unnecessary fields from the reporter in the bugzilla ui if a reporter does not belong to any group. ( if a reporter is in x group it might show and allow him to edited certain fields based on what that x group is ) | ||
'''QA Task: Identify which field are unnecessary. | '''QA Task: Identify which field are unnecessary.''' | ||
''' | |||
Note since many of us have extended privileges in bugzilla an test user without any privileges is needed to exist | Note since many of us have extended privileges in bugzilla an test user without any privileges is needed to exist | ||
so we are able to correctly identify which field(s) need locking or hiding. | so we are able to correctly identify which field(s) need locking or hiding. | ||
'''QA Task: After consensus has been reached on which fields can be removed/hide or locked work with bugzilla maintainers to see this get implemented.''' | '''QA Task: After consensus has been reached on which fields can be removed/hide or locked work with bugzilla maintainers to see this get implemented.''' | ||
== Lack of needed information for maintainer(s) to be able to successfully work with the report. == | == Lack of needed information for maintainer(s) to be able to successfully work with the report. == | ||
Revision as of 15:40, 18 June 2009
QA
Improve reporting in Bugzilla.
Tasks Goal to improver reporting.
Expected result
General Task: Identify what's wrong and what can we do to improve it.
Bugzilla reporting ui to complicated.
When a new reporters enters bugzilla for the first time the current reporting interface might seem to overwhelming to the reporter which leads to all kinds of trouble.
Resolution: Remove/hide or lock ( fields can be visible set to a certain value but none editable ) all unnecessary fields from the reporter in the bugzilla ui if a reporter does not belong to any group. ( if a reporter is in x group it might show and allow him to edited certain fields based on what that x group is )
QA Task: Identify which field are unnecessary.
Note since many of us have extended privileges in bugzilla an test user without any privileges is needed to exist
so we are able to correctly identify which field(s) need locking or hiding.
QA Task: After consensus has been reached on which fields can be removed/hide or locked work with bugzilla maintainers to see this get implemented.
Lack of needed information for maintainer(s) to be able to successfully work with the report.
The reason for the lack of the needed information on a report is in most cases simply that the reporter has not a clue what to include in the report itself.
The underlying problem is not the reporter nor the triager which often ask the reporter to include wrong information because the triager has no better clue what to include in the report so he ask for the most common include case ( usually to include /var/log/messages). The problem is that the maintainer(s) them self have failed to provide this information and for us ( Fedora-QA ) to
When a maintainer introduces a component into Fedora it should be mandatory for him to provide this information along with how to enable debug output and to provide test plans for the component.
Including the test plans however are not relevant to this proposal.
QA Task: Contact FESCO and ask them to set this rule and enforce it. ( New components will not be let into Fedora without this information )