(Created page with '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. Few problems I s...') |
No edit summary |
||
| Line 8: | Line 8: | ||
General Task: Identify what's wrong and what can we do to improve it. | General Task: Identify what's wrong and what can we do to improve it. | ||
Bugzilla reporting ui to complicated. | Bugzilla reporting ui to complicated. | ||
| Line 16: | Line 14: | ||
seem to overwhelming to the reporter which leads to all kinds of trouble. | 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 | 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 be | |||
able to correctly identify which field(s) need locking or hiding. | |||
QA Task: | QA Task: After consensus has been reached on which fields can be removed contact work with bugzilla maintainers those we can remove/hide or lock. | ||
Reports are too vague. | Reports are too vague. | ||
Reports lack needed information for maintainer to be able to | Reports lack needed information for maintainer to be able to | ||
Revision as of 14:41, 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 be able to correctly identify which field(s) need locking or hiding.
QA Task: After consensus has been reached on which fields can be removed contact work with bugzilla maintainers those we can remove/hide or lock.
Reports are too vague. Reports lack needed information for maintainer to be able to