Apache OpenOffice (AOO) Bugzilla – Issue 75692
4 ways to submit issue - need to have one well thought-out
Last modified: 2007-08-28 20:19:12 UTC
We have at least 3 submissions paths to submit new issues: 1. The most obvious one - "New" link (leading to http://www.openoffice.org/issues/enter_bug.cgi) in IssueTracker. It is good in in a way that it gives list of all components WITH descriptions (which is important), but bad in a way that does not promote high quality issues. See illustrating screenshot "subm1.png" - circled in green is list of components, circled in red is the path which leads to the page. 2. The one that forces good behavior, but does not provide list of components with their descriptions - click "My Pages", then "File issue" (leading to http://qa.openoffice.org/issue_handling/pre_submission.html). See illustrating screenshot "subm2.png" - circled in green is the path and circled in green are points the user needs to consider to increase quality. 3. One that is out of the main roads - http://qa.openoffice.org/ooQAReloaded/ooQA-ReportBugs.html, leading to http://qa.openoffice.org/issue_handling/submission_gateway.html. It is sort of OK, but seems redundant. See "subm3.png" - clickpath is shown in blue. I suggest enhancing one of the sumbission pages to include both references to how file good issue (which is essential for reducing load on QA and developers) and provide list of components with descriptions to again aid in filing good issue, and make that page the only submission point.
Created attachment 43897 [details] Screenshot 1
Created attachment 43898 [details] Screenshot 2
Created attachment 43899 [details] Screenshot 1
The QA project takes care of the non-CEE issue handling pages...
Yet another page to submit bug http://qa.openoffice.org/helper.html This one seems to have good instruction.
Dear developers, any progress with this RFE? Thanks a lot for your attention. WBR, Kirill Palagin.
1. We liked to change link 1. to point to 2., but this is not possible due to restrictions in the collab.net framework. I.e., 1. is not fixable. 2. is the "one and only" submission link, at least as far as we can control it. (For instance, in every project except qa, the left-hand link "Report A Bug" leads to this page.) Well, at this this was the intention when introducing it. 3. http://qa.openoffice.org/ooQAReloaded/ooQA-ReportBugs.html nowadays leads to http://qa.openoffice.org/issue_handling/pre_submission.html instead of ../submission_gateway.html, which is correct. I agree that ooQA-ReportBugs.htmlooQA-ReportBugs.html is redundant - more on this later. 4. http://qa.openoffice.org/helper.html is something we were not aware of - I'll add it to the submission gateway as additional option, since this is where it IMO belongs to.
Last part is done - see http://qa.openoffice.org/issue_handling/submission_gateway.html
Also changed http://qa.openoffice.org/issue_handling/pre_submission.html to show the "be registered/logged-in"-requirement more prominently. This is to match the flow on http://qa.openoffice.org/ooQAReloaded/ooQA-ReportBugs.html, which does make sense IMO.
fs->clu:wg: It's up to you now to decided whether http://qa.openoffice.org/ooQAReloaded/ooQA-ReportBugs.html is a "duplicate" of http://qa.openoffice.org/issue_handling/pre_submission.html.
clu,wg: after a longer discussion and analyzing with fs, we came to the conclusion that the current oo qa concept is proper and not redundant 1. more than one way is valid if we want to reach a different part of community - in our case lower experienced oo qa community members (other ones do probably not even visit this side) 2. the 'report bug' side contain more info than the 'pre submission' page and was created by the qa reloaded concept (http://wiki.services.openoffice.org/wiki/QA_reloaded) => direct link to the 'submission gateway' side
clu->kpalagin: for further explanation/discussion, please write me a mail thx
I am glad that we have made progress on this issue. Thanks to everybody. WBR, KP.