Apache OpenOffice (AOO) Bugzilla – Issue 122465
Clear definition for 'Priority' required
Last modified: 2013-06-25 21:21:40 UTC
AOO Bugzilla Help tells: "Priority: Engineers prioritize their bugs using this field. " But how? Is P1 or P5 most important? <https://issues.apache.org/ooo/report.cgi?bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=minor&bug_severity=trivial&chfield=[Bug%20creation]&chfieldfrom=-720d&chfieldto=Now&priority=P1&priority=P2&priority=P4&priority=P5&x_axis_field=bug_severity&y_axis_field=priority&format=table&action=wrap&saved_report_id=1> seems to show that most users consider P1 to have highest priority. But <https://issues.apache.org/ooo/report.cgi?x_axis_field=bug_severity&y_axis_field=priority&z_axis_field=&no_redirect=1&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_id=&bug_id_type=anyexact&votes=&votes_type=greaterthaneq&bug_severity=blocker&bug_severity=critical&priority=P4&priority=P5&emailtype1=substring&email1=&emailtype2=substring&email2=&emailtype3=substring&email3=&chfield=[Bug+creation]&chfieldvalue=&chfieldfrom=-720d&chfieldto=Now&j_top=AND&f1=noop&o1=noop&v1=&format=table&action=wrap> shows that other users think the opposite? I think <https://issues.apache.org/ooo/show_bug.cgi?id=23944#c0> shows the most common way how Priority is used in Bugzilla. So my request: Please describe "Priority" similar to <https://bugzilla.mozilla.org/page.cgi?id=fields.html>
There used to be this description (from the old issue tracker): http://www.openoffice.org/qa/ooQAReloaded/Docs/QA-Reloaded-ITguide.html#priorities
A link to that instruction in BZ Help would be perfect.
And who reads documentations ? ;-) In any case, Apache Infra team manages the BZ server. We only have access to what is available via the admin tool, and that does not include access to the help files. So, we could either open a JIRA issue for the Infra team and give them a patch to apply to the doc. Or maybe better would be to make this definition more prominent in the QA team materials, so new QA members are taught this definition from the start?